Triple
T24054201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yinpterochiroptera |
E595747
|
entity |
| Predicate | sisterTaxon |
P5990
|
FINISHED |
| Object | Yangochiroptera |
—
|
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: Yangochiroptera | Statement: [Yinpterochiroptera, sisterTaxon, Yangochiroptera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sisterTaxon Context triple: [Yinpterochiroptera, sisterTaxon, Yangochiroptera]
-
A.
hasRelatedTaxon
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.
-
B.
taxonomicSynonymOf
Indicates that two taxonomic names refer to the same biological taxon, treating one as an alternative or equivalent scientific name for the other.
-
C.
sisterGroup
chosen
Indicates that two groups share an immediate common ancestor in a hierarchy or classification, making them each other’s closest related group.
-
D.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
E.
parentTaxon
Indicates that one taxonomic group is the immediate higher-level (parent) taxon of another taxonomic group.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9d551288190a2b3b6c8c4f3c1b5 |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:21 p.m.