Triple
T37465183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Phoenix |
E931016
|
entity |
| Predicate | includesExpansion |
P8606
|
FINISHED |
| Object | Ashes of Outland |
E273763
|
NE 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: Ashes of Outland | Statement: [Year of the Phoenix, includesExpansion, Ashes of Outland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesExpansion Context triple: [Year of the Phoenix, includesExpansion, Ashes of Outland]
-
A.
hasExpansion
chosen
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
B.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
C.
belongsToExpansion
Indicates that something is a component or member of a larger expansion set, collection, or release.
-
D.
restrictedExpansionOf
Indicates a relationship where one entity is an expansion of another, but with added constraints or limitations that make it more specific or narrowly applicable than the original.
-
E.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
- F. None of above.
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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a409ef570d08190a937a23dab2b04b1 |
completed | June 28, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.