Triple
T6199355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish monarchy |
E138588
|
entity |
| Predicate | SwedenNorwayUnionPeriod |
P13386
|
FINISHED |
| Object | 1814–1905 |
—
|
LITERAL 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: 1814–1905 | Statement: [Swedish monarchy, SwedenNorwayUnionPeriod, 1814–1905]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SwedenNorwayUnionPeriod Context triple: [Swedish monarchy, SwedenNorwayUnionPeriod, 1814–1905]
-
A.
wasUnderSwedishRuleFrom
Indicates that one entity was governed or controlled by Sweden during a specified time period.
-
B.
unionWithSwedenEnd
Indicates the point in time or event at which a political or territorial union with Sweden comes to an end.
-
C.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
D.
timePeriodAsDanishTerritory
Indicates that, during a specified time period, the referenced place or region was under Danish territorial control or sovereignty.
-
E.
dynasticUnion
chosen
Indicates a political relationship in which two or more distinct states are ruled by the same dynasty or monarch while formally remaining separate entities.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06253534c8190aafe70a6cf5a67ec |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.