Triple
T29561754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandalorians |
E750055
|
entity |
| Predicate | notableArmorFeature |
P32307
|
FINISHED |
| Object | T-shaped visor helmet |
—
|
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: T-shaped visor helmet | Statement: [Mandalorians, notableArmorFeature, T-shaped visor helmet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableArmorFeature Context triple: [Mandalorians, notableArmorFeature, T-shaped visor helmet]
-
A.
notableArmor
Indicates that an entity is recognized for possessing or being associated with armor of particular significance, prominence, or distinction.
-
B.
armorFeature
chosen
Indicates that one entity is a functional or descriptive feature of another entity’s armor.
-
C.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
-
D.
hasArmourCharacteristic
Indicates that an entity possesses a specific armour-related property or feature.
-
E.
armorDescription
Indicates that a descriptive text specifies the characteristics or details of a piece of armor.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 5:20 p.m.