Triple
T37507636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Warcraft patch 9.1 Chains of Domination |
E932137
|
entity |
| Predicate | zoneName |
P169134
|
FINISHED |
| Object | Korthia, the City of Secrets |
—
|
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: Korthia, the City of Secrets | Statement: [World of Warcraft patch 9.1 Chains of Domination, zoneName, Korthia, the City of Secrets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneName Context triple: [World of Warcraft patch 9.1 Chains of Domination, zoneName, Korthia, the City of Secrets]
-
A.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
B.
zoneLabel
chosen
Indicates that a specific label or name is assigned to a defined zone or area within a larger context.
-
C.
zoneStatus
Indicates the current operational or condition state assigned to a specific zone within a system or environment.
-
D.
zoneType
Indicates the classification or category of a zone that specifies its type or functional designation.
-
E.
zoneBased
Indicates that the relationship or action is determined or constrained by specific geographic or logical zones.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.