Triple
T35561849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impero |
E1027654
|
entity |
| Predicate | designedArmorBelt |
P38465
|
FINISHED |
| Object | up to 350 mm |
—
|
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: up to 350 mm | Statement: [Impero, designedArmorBelt, up to 350 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedArmorBelt Context triple: [Impero, designedArmorBelt, up to 350 mm]
-
A.
armorBelt
Indicates that an entity is equipped with or wearing an armor belt as part of its protective gear.
-
B.
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.
-
C.
designedArmor
Indicates that one entity created or planned the armor used or worn by another entity.
-
D.
armoredBeltThickness
chosen
Indicates the thickness of an entity’s protective armored belt in the context of its defensive structure or design.
-
E.
hasPhysicalBelt
Indicates that one entity possesses or is equipped with a physical belt as an item or feature.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
Created at: May 3, 2026, 4:04 p.m.