Triple
T35227999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calopyxis |
E1017149
|
entity |
| Predicate | isTaxonInGroup |
P16820
|
FINISHED |
| Object | Myrtales |
E319683
|
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: Myrtales | Statement: [Calopyxis, isTaxonInGroup, Myrtales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTaxonInGroup Context triple: [Calopyxis, isTaxonInGroup, Myrtales]
-
A.
isTaxonInFamily
Indicates that a given taxon belongs to, or is classified within, a specified biological family.
-
B.
isTaxon
Indicates that one entity is a biological taxonomic unit (such as a species, genus, or family) associated with or classifying another entity.
-
C.
taxonGroup
chosen
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
D.
hasMemberTaxonRank
Indicates that a group or higher-level taxon includes members classified at a specified taxonomic rank.
-
E.
isBySupergroup
Indicates that something (such as a work, event, or item) is created, performed, or produced by a supergroup, i.e., a group formed from members of other established groups.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819d027988190b9236a1405f32483 |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.