Triple
T37705138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungering Destroyer |
E939177
|
entity |
| Predicate | belongsToExpansionContent |
P201864
|
FINISHED |
| Object | Shadowlands endgame |
—
|
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 endgame | Statement: [Hungering Destroyer, belongsToExpansionContent, Shadowlands endgame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToExpansionContent Context triple: [Hungering Destroyer, belongsToExpansionContent, Shadowlands endgame]
-
A.
belongsToExpansion
chosen
Indicates that something is a component or member of a larger expansion set, collection, or release.
-
B.
containsExpandedContent
Indicates that an entity includes additional, more detailed or extended content beyond its standard or primary form.
-
C.
expandsContentFor
Indicates that one entity reveals or displays additional content on behalf of or in relation to another entity.
-
D.
belongsToExtension
Indicates that something is associated with, or is a member/part of, a particular extension (such as a software or file extension).
-
E.
expansionContentType
Indicates the type or category of content that is revealed or added when something is expanded.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0041860fd081908623ef9fd40a9775 |
completed | May 10, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_6a00414b01488190a312adb3b25d69cf |
completed | May 10, 2026, 8:26 a.m. |
Created at: May 3, 2026, 4:18 p.m.