Triple
T37471096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fracture Chambers |
E931153
|
entity |
| Predicate | availableInExpansion |
P100003
|
FINISHED |
| Object | Shadowlands |
—
|
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: Shadowlands | Statement: [Fracture Chambers, availableInExpansion, Shadowlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableInExpansion Context triple: [Fracture Chambers, availableInExpansion, 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.
hasExpansionSetNumber
Indicates that an entity is associated with a specific numbered position or identifier within an expansion set.
-
C.
expansionPack
Indicates that one item serves as an add-on or supplementary content package that extends the features or scope of another item.
-
D.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
E.
mayBeAvailableIn
Indicates that an entity has the potential to be obtainable, accessible, or present within a specified context, location, or medium.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.