Triple
T21652056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Therapsids |
E534361
|
entity |
| Predicate | earEvolution |
P144873
|
FINISHED |
| Object | postdentary bones gave rise to mammalian middle ear ossicles |
—
|
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: postdentary bones gave rise to mammalian middle ear ossicles | Statement: [Therapsids, earEvolution, postdentary bones gave rise to mammalian middle ear ossicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earEvolution Context triple: [Therapsids, earEvolution, postdentary bones gave rise to mammalian middle ear ossicles]
-
A.
earDescription
Indicates a textual description of the characteristics or appearance of an entity’s ear or ears.
-
B.
hearingType
Indicates the type or category of a hearing event or proceeding that takes place.
-
C.
earType
Indicates the specific kind or classification of ears associated with an entity.
-
D.
hearingAbility
Indicates the capacity or level to which an entity can perceive and interpret sound through hearing.
-
E.
earSeveredBy
Indicates that an entity’s ear has been cut off or removed as a result of an action performed by 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef591594a08190bf0ddd0a0c0922ba |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:36 p.m.