Triple
T38584680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mana-Tombs |
E932319
|
entity |
| Predicate | entranceCoordinates |
P189940
|
FINISHED |
| Object | Outland, Terokkar Forest, Auchindoun |
—
|
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: Outland, Terokkar Forest, Auchindoun | Statement: [Mana-Tombs, entranceCoordinates, Outland, Terokkar Forest, Auchindoun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entranceCoordinates Context triple: [Mana-Tombs, entranceCoordinates, Outland, Terokkar Forest, Auchindoun]
-
A.
entranceCoordinatesApprox
chosen
Indicates that the approximate geographic coordinates of an entrance are specified or associated with an entity.
-
B.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
C.
entranceRegion
Indicates the region or area that serves as the entry point or access zone to a place, structure, or space.
-
D.
raidEntranceLocation
Indicates the location where a raid begins or where raiders enter a target area.
-
E.
entranceSize
Indicates the size or dimensions of an entrance relative to a referenced object or structure.
- 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_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:32 p.m.