Triple
T38583642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulduar |
E932297
|
entity |
| Predicate | factionProximity |
P350
|
FINISHED |
| Object | near Sons of Hodir in The Storm Peaks |
—
|
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: near Sons of Hodir in The Storm Peaks | Statement: [Ulduar, factionProximity, near Sons of Hodir in The Storm Peaks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionProximity Context triple: [Ulduar, factionProximity, near Sons of Hodir in The Storm Peaks]
-
A.
featuresRegionalProximity
Indicates that one entity is located near or in close geographic proximity to a particular region or another entity.
-
B.
nearbyInfluence
Indicates that one entity affects or exerts influence on another due to being physically or spatially close to it.
-
C.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
D.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with another entity.
-
E.
near
chosen
Indicates that one entity is located at a short distance from another entity in space or position.
- 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_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:32 p.m.