Triple
T38589980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashkandi, Greatsword of the Brotherhood |
E932430
|
entity |
| Predicate | iconicEra |
P86807
|
FINISHED |
| Object | vanilla World of Warcraft |
—
|
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: vanilla World of Warcraft | Statement: [Ashkandi, Greatsword of the Brotherhood, iconicEra, vanilla World of Warcraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iconicEra Context triple: [Ashkandi, Greatsword of the Brotherhood, iconicEra, vanilla World of Warcraft]
-
A.
visualEra
chosen
Indicates the historical or stylistic period to which the visual appearance or design of something belongs.
-
B.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
C.
depictedPersonEra
Indicates the historical era or time period associated with the person depicted in an image or representation.
-
D.
curatesEra
Indicates a relationship where an entity organizes, selects, or manages items, information, or works specifically associated with a particular historical or thematic era.
-
E.
discoveryEra
Indicates the historical period or era during which the entity was discovered or first identified.
- 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_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.