Triple
T26373456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synapsida |
E660829
|
entity |
| Predicate | containsExtantLineages |
P75991
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Synapsida, containsExtantLineages, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsExtantLineages Context triple: [Synapsida, containsExtantLineages, true]
-
A.
includesExtantTaxa
chosen
Indicates that a group, set, or classification currently contains one or more living (still existing) taxa.
-
B.
hasExtinctBranch
Indicates that an entity has at least one branch, lineage, or subdivision that no longer exists (is extinct).
-
C.
hasExtinctMembers
Indicates that at least some members of the referenced group, class, or category are no longer living or existing.
-
D.
extantSubclade
Indicates that one clade is a currently living (still existing) descendant subgroup within another clade.
-
E.
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).
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 26, 2026, 10:59 p.m.