Triple
T36719266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triglidae |
E907000
|
entity |
| Predicate | headArmor |
P6071
|
FINISHED |
| Object | ossified plates and ridges |
—
|
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: ossified plates and ridges | Statement: [Triglidae, headArmor, ossified plates and ridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headArmor Context triple: [Triglidae, headArmor, ossified plates and ridges]
-
A.
headAttachment
Indicates that one entity is physically or structurally attached to the head or top part of another entity.
-
B.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
C.
armour
chosen
Indicates that an entity provides protective covering or defense for another entity.
-
D.
hasCasque
Indicates that one entity possesses, wears, or is equipped with a casque (a type of helmet or protective headgear).
-
E.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c84319dc8190987c08469720d6b1 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.