Triple
T32136255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RedPepperFlakes |
E820769
|
entity |
| Predicate | originPlantGenus |
P111175
|
FINISHED |
| Object | Capsicum |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Capsicum | Statement: [RedPepperFlakes, originPlantGenus, Capsicum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originPlantGenus Context triple: [RedPepperFlakes, originPlantGenus, Capsicum]
-
A.
plantGenus
chosen
Indicates that one entity is a biological genus to which the plant entity belongs.
-
B.
hostsPlantOf
Indicates that one entity serves as a host environment or substrate on which a particular plant lives, grows, or depends.
-
C.
cultivarOrigin
Indicates that a particular plant cultivar was originally developed, bred, or derived from a specified source location, population, or lineage.
-
D.
associatedRootGenus
Indicates that one entity is taxonomically linked or connected as a root genus to another entity.
-
E.
hostPlantFamily
Indicates the taxonomic plant family that serves as the host for a given organism, typically providing it with food, shelter, or a site for development.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a016ebba0448190b5319243e1b2feca |
completed | May 11, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a016d2486b4819085efe197ee21b707 |
completed | May 11, 2026, 5:46 a.m. |
Created at: May 1, 2026, 12:30 a.m.