Triple
T37552158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormheim |
E933612
|
entity |
| Predicate | hasQuestline |
P181488
|
FINISHED |
| Object | Alliance Stormheim campaign |
—
|
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: Alliance Stormheim campaign | Statement: [Stormheim, hasQuestline, Alliance Stormheim campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuestline Context triple: [Stormheim, hasQuestline, Alliance Stormheim campaign]
-
A.
hasQuestContentIn
Indicates that a quest’s narrative or objectives are contained within or associated with a particular location, context, or container.
-
B.
questlineAvailableIn
chosen
Indicates that a particular questline can be accessed or played within a specified game, mode, or context.
-
C.
hasQuestHubIn
Indicates that a quest hub is located within or associated with a particular place or region.
-
D.
hasMissionTo
Indicates that an entity is assigned or dedicated to carrying out a specific mission, task, or purpose related to another entity or objective.
-
E.
hasQuestElement
Indicates that something is a component, step, or requirement that forms part of a larger quest or mission.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.