Triple
T32978695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tetrapoda |
E843738
|
entity |
| Predicate | includesExtinct |
P29528
|
FINISHED |
| Object | early stem tetrapods |
—
|
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: early stem tetrapods | Statement: [Tetrapoda, includesExtinct, early stem tetrapods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesExtinct Context triple: [Tetrapoda, includesExtinct, early stem tetrapods]
-
A.
includesExtinctGenera
Indicates that the referenced taxonomic group or set contains one or more genera that are extinct.
-
B.
includesExtinctFamily
Indicates that the subject group or category contains at least one family that is no longer extant (i.e., all its member species are extinct).
-
C.
hasExtinctSpecies
chosen
Indicates that at least one species associated with the subject entity is no longer extant (i.e., has gone extinct).
-
D.
hasExtinction
Indicates that an entity has undergone, is subject to, or is associated with an extinction event or state of no longer existing.
-
E.
titleExtinct
Indicates that a formal title or rank is no longer in existence or officially recognized.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0224f4b6cc8190a8f79700a9af765f |
completed | May 11, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_6a0223f01eb081909419518fdd45f2a4 |
completed | May 11, 2026, 6:46 p.m. |
Created at: May 1, 2026, 1:22 a.m.