Triple
T38587282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockade Prison |
E932372
|
entity |
| Predicate | questHubAssociation |
P99971
|
FINISHED |
| Object | Stormwind City |
—
|
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: Stormwind City | Statement: [Stockade Prison, questHubAssociation, Stormwind City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questHubAssociation Context triple: [Stockade Prison, questHubAssociation, Stormwind City]
-
A.
questHubFor
chosen
Indicates a relationship where one entity serves as the central location or main coordination point for quests associated with another entity.
-
B.
questHubNPC
Indicates that an NPC serves as a central provider or coordinator of quests for players.
-
C.
tourAssociation
Indicates a relationship where an entity is linked or affiliated with a specific tour, such as organizing, sponsoring, or being formally connected to that tour.
-
D.
questlineFeature
Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
-
E.
associatedWonder
Indicates a relationship where one entity is linked or connected to a particular wonder, such as a notable marvel, attraction, or extraordinary feature.
- 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_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:32 p.m.