Triple
T11088068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweden–Norway |
E262174
|
entity |
| Predicate | hadSeparateConstitutions |
P97154
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sweden–Norway, hadSeparateConstitutions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSeparateConstitutions Context triple: [Sweden–Norway, hadSeparateConstitutions, true]
-
A.
constitutions
Indicates that one entity formally establishes, composes, or makes up the essential structure or legal foundation of another entity.
-
B.
haveDistinctMonarchicHistories
Indicates that the entities have different historical experiences or developments related to monarchic rule or monarchy as a political system.
-
C.
numberOfConstitutionsPreviouslyInForce
Indicates the count of distinct constitutions that were officially in force before the current one.
-
D.
previousConstitution
Indicates that one constitution temporally precedes and was in force before another constitution in a given legal or political system.
-
E.
regionOfConfederation
Indicates that a given region belongs to, is part of, or is administered within a particular confederation.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c5008081908f59612243fa4f7a |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.