Triple
T38592137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarab Wall |
E932477
|
entity |
| Predicate | gatesAccess |
P15393
|
FINISHED |
| Object | Ruins 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: Ruins of Ahn'Qiraj | Statement: [Scarab Wall, gatesAccess, Ruins of Ahn'Qiraj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gatesAccess Context triple: [Scarab Wall, gatesAccess, Ruins of Ahn'Qiraj]
-
A.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
B.
gateWeight
Indicates the weight or importance assigned to a particular gate or transition within a process, model, or system.
-
C.
gateType
Indicates the specific kind or classification of a gate associated with an entity.
-
D.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
E.
controlsAccessTo
chosen
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
- 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_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.