Triple
T38591547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruins of Ahn'Qiraj |
E932464
|
entity |
| Predicate | sharesEntranceAreaWith |
P23812
|
FINISHED |
| Object | Temple of Ahn'Qiraj |
—
|
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: Temple of Ahn'Qiraj | Statement: [Ruins of Ahn'Qiraj, sharesEntranceAreaWith, Temple of Ahn'Qiraj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesEntranceAreaWith Context triple: [Ruins of Ahn'Qiraj, sharesEntranceAreaWith, Temple of Ahn'Qiraj]
-
A.
sharesCorridorWith
Indicates that two entities are located along or connected by the same corridor or passageway.
-
B.
sharesTerminalAreaWith
Indicates that two entities occupy or are associated with the same terminal area or zone.
-
C.
sharesAreaWith
chosen
Indicates that two entities occupy or overlap the same geographic or spatial area.
-
D.
sharesFacilityWith
Indicates that two entities use or have access to the same physical facility or location.
-
E.
sharesArenaWith
Indicates that two entities use or occupy the same arena as a common venue or location.
- 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_6a00d6aff0a08190a330dd0c7c1352f9 |
completed | May 10, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a00d60f2a508190aeaf5a9d8af9c39e |
completed | May 10, 2026, 7:01 p.m. |
Created at: May 3, 2026, 4:32 p.m.