Triple
T37508875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigilant Guardian |
E932165
|
entity |
| Predicate | expansionPatchContext |
P192411
|
FINISHED |
| Object | late Shadowlands raid tier |
—
|
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: late Shadowlands raid tier | Statement: [Vigilant Guardian, expansionPatchContext, late Shadowlands raid tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionPatchContext Context triple: [Vigilant Guardian, expansionPatchContext, late Shadowlands raid tier]
-
A.
expansionPatch
Indicates that an entity serves as an extension or add-on that enlarges or augments another entity’s existing scope, content, or functionality.
-
B.
expansionZoneContext
Indicates the contextual conditions or parameters under which an expansion zone is defined, interpreted, or applied within a broader system or process.
-
C.
expansionReleaseContext
chosen
Indicates the context or circumstances under which an expansion (e.g., of a product, content, or feature) is released.
-
D.
expansionSystem
Indicates a relationship where a system undergoes or enables expansion, typically by increasing its scope, capacity, or components over time.
-
E.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.