Triple
T36209898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Methuselah Trail |
E1047508
|
entity |
| Predicate | hasNotableTreeType |
P6706
|
FINISHED |
| Object | Great Basin bristlecone pine |
E25030
|
NE 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: Great Basin bristlecone pine | Statement: [Methuselah Trail, hasNotableTreeType, Great Basin bristlecone pine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTreeType Context triple: [Methuselah Trail, hasNotableTreeType, Great Basin bristlecone pine]
-
A.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
B.
hasTree
chosen
Indicates that one entity possesses, contains, or is associated with a tree.
-
C.
hasNotableClientType
Indicates that an entity has clients belonging to a particular notable or distinguished category or type.
-
D.
hasNotableBandType
Indicates that an entity is associated with a band of a particular notable type or category.
-
E.
hasNotableNamesakeType
Indicates that an entity has a notable namesake of a specified type (such as a person, place, or work) that shares its name.
- F. None of above.
Provenance (4 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39342349748190a08aa6dd11710d38 |
completed | June 22, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.