Triple
T37470688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kleia |
E931143
|
entity |
| Predicate | expansionSetting |
P192016
|
FINISHED |
| Object | Shadowlands |
—
|
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 | Statement: [Kleia, expansionSetting, Shadowlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionSetting Context triple: [Kleia, expansionSetting, Shadowlands]
-
A.
expandsSetting
Indicates that one entity broadens, elaborates, or adds detail to the contextual setting established by another entity.
-
B.
expansionOptions
Indicates the available ways or configurations in which something can be extended, enlarged, or further developed.
-
C.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
D.
expansionParameter
Indicates a parameter that controls or characterizes how something expands, such as the rate, extent, or manner of its expansion.
-
E.
expansionSystem
Indicates a relationship where a system undergoes or enables expansion, typically by increasing its scope, capacity, or components over time.
- 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_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
| PDg | Predicate description generation | batch_69fcf1b241888190a243f07051c71383 |
completed | May 7, 2026, 8:10 p.m. |
Created at: May 3, 2026, 4:17 p.m.