Triple
T35228102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminaliopsis |
E1017153
|
entity |
| Predicate | closelyRelatedGenus |
P51064
|
FINISHED |
| Object | Terminalia |
—
|
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: Terminalia | Statement: [Terminaliopsis, closelyRelatedGenus, Terminalia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closelyRelatedGenus Context triple: [Terminaliopsis, closelyRelatedGenus, Terminalia]
-
A.
closelyRelatedVariety
Indicates that one variety is very similar to another, differing only in minor or closely related characteristics.
-
B.
closelyRelatedConcept
Indicates that two concepts share a strong, direct, and meaningful connection in meaning, function, or usage.
-
C.
hasRelatedTaxon
chosen
Indicates a taxonomic relationship between two taxa that are connected in some biologically or taxonomically relevant way, without specifying the exact nature of that relationship.
-
D.
hasNamesakeGenus
Indicates that one entity serves as the namesake for a biological genus named after it.
-
E.
associatedRootGenus
Indicates that one entity is taxonomically linked or connected as a root genus to another entity.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.