Triple
T15239205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmontosaurus annectens |
E364209
|
entity |
| Predicate | crestPresence |
P24643
|
FINISHED |
| Object | lacked large bony cranial crest |
—
|
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: lacked large bony cranial crest | Statement: [Edmontosaurus annectens, crestPresence, lacked large bony cranial crest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crestPresence Context triple: [Edmontosaurus annectens, crestPresence, lacked large bony cranial crest]
-
A.
crestElement
Indicates that one entity is a crest or emblematic design element associated with, or forming part of, another entity.
-
B.
crest
Indicates reaching the highest point or peak of something, such as a wave, hill, or trend, before it begins to decline.
-
C.
confirmedPresenceOf
Indicates that the presence or existence of an entity has been verified as true or established with certainty.
-
D.
crestFeature
chosen
Indicates that an entity possesses a notable crest-related characteristic or structural feature.
-
E.
notablePresence
Indicates that an entity has a significant or prominent presence in relation to another entity, context, or domain.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007db9a148190aadea8d5f8b6b261 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.