Triple
T35946983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ticodendron |
E1039609
|
entity |
| Predicate | describedAsNewGenus |
P194392
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ticodendron, describedAsNewGenus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedAsNewGenus Context triple: [Ticodendron, describedAsNewGenus, true]
-
A.
firstDescribedAsGenusBy
Indicates that one entity was the first to formally describe another entity as a genus in a taxonomic or scientific context.
-
B.
exampleGenus
Indicates that one entity is an example or instance illustrating the genus or general category represented by the other entity.
-
C.
describedAsSpecies
Indicates that one entity is characterized or identified as a particular species in relation to another entity.
-
D.
describedAsSmallGenus
Indicates that something is characterized or classified as a small genus in a taxonomic or categorical context.
-
E.
describedTaxon
Indicates that an entity (such as a publication or description) formally describes or establishes the referenced taxon.
- F. None of above. chosen
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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: May 3, 2026, 4:07 p.m.