Triple
T35830700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadwind Pass |
E1035788
|
entity |
| Predicate | inGameRegion |
P100146
|
FINISHED |
| Object | Southern Eastern Kingdoms |
—
|
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: Southern Eastern Kingdoms | Statement: [Deadwind Pass, inGameRegion, Southern Eastern Kingdoms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inGameRegion Context triple: [Deadwind Pass, inGameRegion, Southern Eastern Kingdoms]
-
A.
regionInGame
Indicates that a specific region or area exists within or is part of a particular game.
-
B.
inGameZone
chosen
Indicates that an entity is located within a defined game zone or area of the game world.
-
C.
isPlayedInRegion
Indicates that an instance of something (such as a game, media, or event) is available to be played or occurs within a specified geographic region.
-
D.
hasPrimaryGameRegion
Indicates that an entity is associated with a main or principal geographic region in which a game is released, played, or targeted.
-
E.
playerBaseRegion
Indicates the geographic region or area that serves as the primary base or home location for a player.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:06 p.m.