Triple
T38584242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tempest Keep – The Eye |
E932309
|
entity |
| Predicate | expansionZoneCategory |
P194162
|
FINISHED |
| Object | Outland raid |
—
|
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: Outland raid | Statement: [Tempest Keep – The Eye, expansionZoneCategory, Outland raid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionZoneCategory Context triple: [Tempest Keep – The Eye, expansionZoneCategory, Outland raid]
-
A.
expansionZoneContext
Indicates the contextual conditions or parameters under which an expansion zone is defined, interpreted, or applied within a broader system or process.
-
B.
expansionRegion
Indicates a region or area into which something (such as a structure, process, or influence) is intended or allowed to expand.
-
C.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
D.
expansionUnit
Indicates a unit or component that serves to extend, enlarge, or add capacity to another system, structure, or entity.
-
E.
zonesInclude
Indicates that one zone spatially or logically contains or encompasses another zone.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69fd64bb345c819096a35c72784a8ce3 |
completed | May 8, 2026, 4:21 a.m. |
Created at: May 3, 2026, 4:32 p.m.