Triple
T15239342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nodosauridae |
E364212
|
entity |
| Predicate | armorDistribution |
P32307
|
FINISHED |
| Object | dorsal armor |
—
|
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: dorsal armor | Statement: [Nodosauridae, armorDistribution, dorsal armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armorDistribution Context triple: [Nodosauridae, armorDistribution, dorsal armor]
-
A.
armorFeature
chosen
Indicates that one entity is a functional or descriptive feature of another entity’s armor.
-
B.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
C.
armorBelt
Indicates that an entity is equipped with or wearing an armor belt as part of its protective gear.
-
D.
armorGeneration
Indicates the creation or provision of protective armor for an entity, often as a result of some action, ability, or process.
-
E.
armorType
Indicates the specific category or classification of protective armor 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_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.