Triple
T37470306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbiter’s Chamber |
E931135
|
entity |
| Predicate | firstIntroducedInExpansion |
P100003
|
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: [Arbiter’s Chamber, firstIntroducedInExpansion, Shadowlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIntroducedInExpansion Context triple: [Arbiter’s Chamber, firstIntroducedInExpansion, Shadowlands]
-
A.
introducedInExpansion
chosen
Indicates that something (such as a feature, item, or concept) was first added or made available as part of a specific expansion.
-
B.
introducedExpansion
Indicates that an entity caused a new expansion, extension, or enlargement of something to be brought into existence or put into use.
-
C.
introducedInGameAs
Indicates that an entity first appeared or was made available within a specific game title.
-
D.
appearsInGameExpansion
Indicates that an entity is featured or included within a specific game expansion.
-
E.
hasExpansionSetNumber
Indicates that an entity is associated with a specific numbered position or identifier within an expansion set.
- 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_69f76ec2af148190897d101070d7f415 |
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_6a40cda3bc308190a50033a23640c1c2 |
completed | June 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.