Triple
T38584046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eversong Woods |
E932305
|
entity |
| Predicate | expansionAddedIn |
P98691
|
FINISHED |
| Object | The Burning Crusade |
—
|
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: The Burning Crusade | Statement: [Eversong Woods, expansionAddedIn, The Burning Crusade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionAddedIn Context triple: [Eversong Woods, expansionAddedIn, The Burning Crusade]
-
A.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
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.
expansionPack
chosen
Indicates that one item serves as an add-on or supplementary content package that extends the features or scope of another item.
-
D.
expansionOptions
Indicates the available ways or configurations in which something can be extended, enlarged, or further developed.
-
E.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
- 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_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:32 p.m.