Triple
T7592549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian politics |
E179773
|
entity |
| Predicate | constitutionalMonarchy |
P8695
|
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: [Norwegian politics, constitutionalMonarchy, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constitutionalMonarchy Context triple: [Norwegian politics, constitutionalMonarchy, true]
-
A.
constitutionalMonarchyFeature
Indicates that the subject possesses a characteristic or institutional element typical of a constitutional monarchy system of government.
-
B.
constitutionalMonarchyEstablished
Indicates that a constitutional monarchy as a system of government has been formally created or brought into existence.
-
C.
monarchy
Indicates a system of governance in which supreme authority is vested in a single ruler, typically a king or queen, whose position is usually hereditary.
-
D.
monarchyStatus
chosen
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
-
E.
headOfStateIsAlsoHeadOfGovernment
Indicates that the same individual holds both the role of head of state and the role of head of government.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9b92c348190b547f0aacfb8d6be |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.