Triple
T38583025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highmountain tauren |
E932286
|
entity |
| Predicate | heritageArmor |
P47329
|
FINISHED |
| Object | Highmountain Heritage Armor |
—
|
NE NERFINISHED |
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: Highmountain Heritage Armor | Statement: [Highmountain tauren, heritageArmor, Highmountain Heritage Armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageArmor Context triple: [Highmountain tauren, heritageArmor, Highmountain Heritage Armor]
-
A.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
B.
designedArmor
Indicates that one entity created or planned the armor used or worn by another entity.
-
C.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
D.
notableArmor
chosen
Indicates that an entity is recognized for possessing or being associated with armor of particular significance, prominence, or distinction.
-
E.
armorVariant
Indicates that one armor is a specific version, type, or modification derived from another 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 3, 2026, 4:32 p.m.