Triple
T37459889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anub'Rekhan |
E930891
|
entity |
| Predicate | locationWing |
P94409
|
FINISHED |
| Object | The Arachnid Quarter |
E930887
|
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: The Arachnid Quarter | Statement: [Anub'Rekhan, locationWing, The Arachnid Quarter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationWing Context triple: [Anub'Rekhan, locationWing, The Arachnid Quarter]
-
A.
roofLocation
Indicates that one entity is located on, at, or forming the roof of another entity.
-
B.
chamberLocatedIn
Indicates that a chamber is physically situated within or inside a specified larger location or structure.
-
C.
locationInArchitecture
Indicates the spatial position or placement of one architectural element or feature within or relative to another architectural structure or context.
-
D.
locatedInSectionOfBuilding
chosen
Indicates that one entity is situated within a specific section or area of a building.
-
E.
doorLocation
Indicates the spatial position or placement of a door relative to a reference structure or area.
- F. None of above.
Provenance (4 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a408c2fd1008190b1d22ac3d5ae05a0 |
completed | June 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.