Triple
T37471573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrian (language) |
E931165
|
entity |
| Predicate | settingExpansion |
P194789
|
FINISHED |
| Object | Shadowlands expansion |
—
|
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 expansion | Statement: [Kyrian (language), settingExpansion, Shadowlands expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingExpansion Context triple: [Kyrian (language), settingExpansion, Shadowlands expansion]
-
A.
expansionSetting
Indicates the configuration or parameters that determine how something is expanded, extended, or unfolded in scope, size, or detail.
-
B.
expansionTier
Indicates the level or category of expansion associated with an entity, such as its stage, scope, or priority in an expansion process.
-
C.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
D.
expansionPack
Indicates that one item serves as an add-on or supplementary content package that extends the features or scope of another item.
-
E.
expansionOptions
Indicates the available ways or configurations in which something can be extended, enlarged, or further developed.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
| PDg | Predicate description generation | batch_69fd8640e1d4819081c98f15eeb221ab |
completed | May 8, 2026, 6:44 a.m. |
Created at: May 3, 2026, 4:17 p.m.