Triple
T37541604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death (Warcraft cosmology) |
E933337
|
entity |
| Predicate | hasPrimaryPlane |
P205969
|
FINISHED |
| Object | Shadowlands |
E273800
|
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: Shadowlands | Statement: [Death (Warcraft cosmology), hasPrimaryPlane, Shadowlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryPlane Context triple: [Death (Warcraft cosmology), hasPrimaryPlane, Shadowlands]
-
A.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
B.
hasPrimarySystem
Indicates that an entity is associated with or operates under a main or principal system among potentially multiple systems.
-
C.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
D.
hasPrimaryPlatform
Indicates that one entity is designated as the main or principal platform associated with another entity.
-
E.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d12d0548190b0102321d381c2ac |
completed | June 28, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.