Triple
T26705959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avemetatarsalia |
E673288
|
entity |
| Predicate | includesMajorSubclade |
P10936
|
FINISHED |
| Object | Ornithodira |
—
|
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: Ornithodira | Statement: [Avemetatarsalia, includesMajorSubclade, Ornithodira]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMajorSubclade Context triple: [Avemetatarsalia, includesMajorSubclade, Ornithodira]
-
A.
extantSubclade
Indicates that one clade is a currently living (still existing) descendant subgroup within another clade.
-
B.
belongsToSubfamily
Indicates that one entity is a member of, or classified within, a specific subfamily of another entity.
-
C.
recognizesClade
Indicates that one entity acknowledges or accepts another entity as a valid clade or monophyletic group in a classification or phylogenetic context.
-
D.
belongsToClade
chosen
Indicates that an organism or taxonomic group is a member of, or included within, a specified evolutionary clade.
-
E.
isLargestSubfamilyOf
Indicates that one group or category is the largest subfamily within another, typically in terms of number of members or size.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 27, 2026, 3:34 a.m.