Triple
T31577531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Platydoras |
E805735
|
entity |
| Predicate | hasBodyArmor |
P132245
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Platydoras, hasBodyArmor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyArmor Context triple: [Platydoras, hasBodyArmor, yes]
-
A.
hasTypicalArmor
Indicates that an entity normally wears or is equipped with a standard or characteristic type of armor.
-
B.
hasArmorPlating
chosen
Indicates that one entity is equipped with or covered by protective armor plating in relation to another entity or context.
-
C.
wearsArmor
Indicates that an entity is equipped with or dressed in armor as protective gear.
-
D.
armourBelt
Indicates a relationship where an armour belt is equipped on, attached to, or associated with an entity (such as a character, vehicle, or structure) as protective gear.
-
E.
wearsArmorOf
Indicates that one entity is equipped with or dressed in the specific armor that belongs to or is associated with another 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 30, 2026, 10:22 p.m.