Triple
T26706083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceratopsia |
E673290
|
entity |
| Predicate | frillFunction |
P161144
|
FINISHED |
| Object | likely used for 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: likely used for display | Statement: [Ceratopsia, frillFunction, likely used for display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frillFunction Context triple: [Ceratopsia, frillFunction, likely used for display]
-
A.
hasFrill
Indicates that one entity possesses or is characterized by a frill as a distinguishing feature or component.
-
B.
fringes
Indicates that one entity forms or constitutes the border, edge, or peripheral boundary of another entity.
-
C.
veilFunction
Indicates a relationship where something serves as or provides the function of a veil, typically obscuring, concealing, or partially covering something else.
-
D.
fruitFunction
Indicates that something serves as the functional role or primary use of a fruit (e.g., nutritional, culinary, or reproductive purpose).
-
E.
fimbriationColor
Indicates the color used for the fimbriation (the narrow bordering or edging) around an element.
- 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_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. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 3:34 a.m.