Triple
T27506133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ichthyornis |
E694281
|
entity |
| Predicate | hadModernLikePectoralGirdle |
P162668
|
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: [Ichthyornis, hadModernLikePectoralGirdle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadModernLikePectoralGirdle Context triple: [Ichthyornis, hadModernLikePectoralGirdle, true]
-
A.
ribcageMorphology
Indicates the structural form, shape, and configuration of a ribcage in an organism.
-
B.
cranialCapacityComparedToEarlierHominins
Indicates that the subject’s cranial capacity is being evaluated in relation to, and characterized as larger, smaller, or similar compared to, that of earlier hominin species.
-
C.
hasHomininTaxon
Indicates that an entity is associated with, classified under, or belongs to a particular hominin taxonomic group.
-
D.
fossilMorphology
Indicates that one entity describes or characterizes the physical form and structural features of a fossil associated with another entity.
-
E.
earliestKnownAncestor
Indicates that one entity is the most distant (oldest) known ancestor in the lineage of another entity.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ec6fae8819087eacb7e498113b5 |
completed | May 2, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62cd1912c8190ab3f3288442115a4 |
completed | May 2, 2026, 4:56 p.m. |
Created at: April 27, 2026, 1:13 p.m.