Triple
T7577365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diapsida |
E179391
|
entity |
| Predicate | endothermicLineages |
P77576
|
FINISHED |
| Object | birds |
—
|
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: birds | Statement: [Diapsida, endothermicLineages, birds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endothermicLineages Context triple: [Diapsida, endothermicLineages, birds]
-
A.
extantSubclade
Indicates that one clade is a currently living (still existing) descendant subgroup within another clade.
-
B.
evolvesIn
Indicates that an entity undergoes a process of change or development within a specified environment, context, or medium.
-
C.
laterSpecies
Indicates that one species appears or evolves later in time relative to another species.
-
D.
endemicLegacy
Indicates that a condition, trait, or influence is persistently rooted and locally confined to a particular context, region, or population as a lasting effect.
-
E.
evolvedIn
Indicates that an entity originated or developed within a specified environment, context, or location over evolutionary time.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f94cdbec81909f2ba7ce04e49931 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f5b1a6a08190b9ff2bc8a7befe0d |
completed | March 27, 2026, 9:25 p.m. |
Created at: March 27, 2026, 3:51 p.m.