Triple
T2666814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceratocystis |
E55654
|
entity |
| Predicate | hostExample |
P2592
|
FINISHED |
| Object | cacao (Theobroma cacao) |
—
|
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: cacao (Theobroma cacao) | Statement: [Ceratocystis, hostExample, cacao (Theobroma cacao)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostExample Context triple: [Ceratocystis, hostExample, cacao (Theobroma cacao)]
-
A.
host
chosen
Indicates that one entity provides space, resources, or services to accommodate, receive, or entertain another entity.
-
B.
hostsBody
Indicates that one entity serves as the physical container or location in which another entity resides or is situated.
-
C.
hostGalaxy
Indicates the galaxy in which an astronomical object or system is located or with which it is physically associated.
-
D.
exampleDomain
Indicates a general or illustrative relationship used as a placeholder within a specific conceptual or application domain.
-
E.
hostStar
Indicates that one celestial object serves as the primary star around which another object, such as a planet or system, is associated or orbits.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd97040e48190b0a87489f108810e |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.