Triple
T38588544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for Lordaeron |
E932399
|
entity |
| Predicate | expansionLaunchContent |
P192411
|
FINISHED |
| Object | Battle for Azeroth pre-patch |
—
|
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: Battle for Azeroth pre-patch | Statement: [Battle for Lordaeron, expansionLaunchContent, Battle for Azeroth pre-patch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionLaunchContent Context triple: [Battle for Lordaeron, expansionLaunchContent, Battle for Azeroth pre-patch]
-
A.
expandsContentFor
Indicates that one entity reveals or displays additional content on behalf of or in relation to another entity.
-
B.
expansionContentType
Indicates the type or category of content that is revealed or added when something is expanded.
-
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.
editorExpandedContent
Indicates that an editor interface or component is in an expanded (as opposed to collapsed) state, showing additional content or options.
-
E.
expansionReleaseContext
chosen
Indicates the context or circumstances under which an expansion (e.g., of a product, content, or feature) is released.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:32 p.m.