Triple
T20854799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gustavian era |
E513451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | period of Swedish history |
C18380
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: period of Swedish history Context triple: [Gustavian era, instanceOf, period of Swedish history]
-
A.
era in Swedish history
chosen
An era in Swedish history is a distinct period characterized by specific political structures, social conditions, cultural developments, and economic patterns that together define a recognizable phase in Sweden’s historical timeline.
-
B.
historical province of Sweden
A historical province of Sweden is a traditional geographic and cultural region with historical significance, distinct identity, and often unique customs, which no longer serves as an administrative unit but remains important in cultural and regional contexts.
-
C.
era of English history
An era of English history is a distinct period characterized by particular political structures, social conditions, cultural developments, and significant events that collectively differentiate it from other times in England’s past.
-
D.
historical period
A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
-
E.
event in Danish history
A significant occurrence or series of actions situated in Denmark’s past that influenced its political, social, cultural, or economic development.
- F. None of above.
Provenance (1 batch)
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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:44 p.m.