Triple
T26706019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadrosauridae |
E673289
|
entity |
| Predicate | crestFunctionHypothesis |
P14769
|
FINISHED |
| Object | visual display |
—
|
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: visual display | Statement: [Hadrosauridae, crestFunctionHypothesis, visual display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crestFunctionHypothesis Context triple: [Hadrosauridae, crestFunctionHypothesis, visual display]
-
A.
crest
Indicates reaching the highest point or peak of something, such as a wave, hill, or trend, before it begins to decline.
-
B.
crestElement
Indicates that one entity is a crest or emblematic design element associated with, or forming part of, another entity.
-
C.
functionHypothesis
chosen
Indicates that an entity is proposed or assumed to serve as a function or functional explanation for another entity or phenomenon.
-
D.
crestFeature
Indicates that an entity possesses a notable crest-related characteristic or structural feature.
-
E.
crestType
Indicates the specific style or form of a crest associated with an entity.
- 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_69f617b9d9648190a1f50ece0815b857 |
completed | May 2, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:34 a.m.