Triple
T26921012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbimorphae |
E677644
|
entity |
| Predicate | sisterCladeOf |
P5990
|
FINISHED |
| Object | Otidimorphae |
—
|
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: Otidimorphae | Statement: [Columbimorphae, sisterCladeOf, Otidimorphae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sisterCladeOf Context triple: [Columbimorphae, sisterCladeOf, Otidimorphae]
-
A.
sisterGroup
chosen
Indicates that two groups share an immediate common ancestor in a hierarchy or classification, making them each other’s closest related group.
-
B.
belongsToClade
Indicates that an organism or taxonomic group is a member of, or included within, a specified evolutionary clade.
-
C.
siblingBranch
Indicates that two branches share the same immediate parent node in a hierarchical structure, making them parallel or peer branches.
-
D.
supercladeOf
Indicates that one clade is a broader, more inclusive clade that contains another clade as a subset within a phylogenetic or taxonomic hierarchy.
-
E.
proposedClade
Indicates that one entity is hypothesized to form a clade with another (or others), representing a suggested but not necessarily confirmed evolutionary grouping.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6200cee788190ba32d1379b50ba57 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:07 a.m.