Triple
T37471230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Upper Reaches |
E931156
|
entity |
| Predicate | expansionPatch |
P192106
|
FINISHED |
| Object | Shadowlands launch |
—
|
LITERAL 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 launch | Statement: [The Upper Reaches, expansionPatch, Shadowlands launch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionPatch Context triple: [The Upper Reaches, expansionPatch, Shadowlands launch]
-
A.
expansionPack
Indicates that one item serves as an add-on or supplementary content package that extends the features or scope of another item.
-
B.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
C.
expansionSystem
Indicates a relationship where a system undergoes or enables expansion, typically by increasing its scope, capacity, or components over time.
-
D.
expansionProject
Indicates a project whose primary purpose is to enlarge, extend, or increase the capacity, scope, or reach of something.
-
E.
expansionUnit
Indicates a unit or component that serves to extend, enlarge, or add capacity to another system, structure, or entity.
- F. None of above. chosen
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_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:17 p.m.