Triple
T6199337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish monarchy |
E138588
|
entity |
| Predicate | currentConstitutionCameIntoForce |
P762
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [Swedish monarchy, currentConstitutionCameIntoForce, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentConstitutionCameIntoForce Context triple: [Swedish monarchy, currentConstitutionCameIntoForce, 1975]
-
A.
yearEnteredIntoForce
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
-
B.
constitutionEffectiveFrom
chosen
Indicates the date or point in time from which a particular constitution or constitutional provision is legally in force and applicable.
-
C.
lastConstitutionAdopted
Indicates that a particular constitution was the most recently adopted constitution of a given political entity or jurisdiction.
-
D.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
E.
servedAsConstitutionUntil
Indicates that one document functioned as the official constitution of an entity up to a specified point in time.
- 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.