Triple
T38022594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Rastakhan |
E948680
|
entity |
| Predicate | locationDuringBfA |
P207562
|
FINISHED |
| Object | Dazar'alor |
E939176
|
NE 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: Dazar'alor | Statement: [King Rastakhan, locationDuringBfA, Dazar'alor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationDuringBfA Context triple: [King Rastakhan, locationDuringBfA, Dazar'alor]
-
A.
currentlyLocatedAt
Indicates that an entity’s present or most recent known physical location is at the specified place.
-
B.
locationOnField
Indicates the specific position or area that an entity occupies on a defined field or playing surface.
-
C.
locationInPlay
Indicates that an entity is currently situated or active within the defined play area or game environment.
-
D.
locationDuringUse
Indicates the place or spatial context where an entity is situated specifically while it is being used or in active operation.
-
E.
locatedOnLevel
Indicates that one entity is situated on a specific floor or level within a multi-level structure or system.
- F. None of above. chosen
Provenance (5 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41543d43708190a6d6e8da5b6e41e2 |
completed | June 28, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037df009f4819082e04683e6e8a106 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:20 p.m.