Triple
T25630339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya world tree |
E642553
|
entity |
| Predicate | associatedTreeSpecies |
P966
|
FINISHED |
| Object | Ceiba pentandra |
—
|
NE NERFINISHED |
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: Ceiba pentandra | Statement: [Maya world tree, associatedTreeSpecies, Ceiba pentandra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTreeSpecies Context triple: [Maya world tree, associatedTreeSpecies, Ceiba pentandra]
-
A.
notableTreeSpecies
chosen
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
B.
favoriteTrees
Indicates that one or more trees are preferred over others by a given entity.
-
C.
commonTreeType
Indicates that two or more entities share the same type or classification of tree.
-
D.
treeHabit
Indicates the growth form or structural habit characteristic of a tree, such as its typical shape, branching pattern, or overall stature.
-
E.
formerSummitTreeSpecies
Indicates that a species previously dominated or characterized the tree community at a summit but no longer does so.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 21, 2026, 5:17 p.m.