Triple
T36450403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian referendum on monarchy |
E897992
|
entity |
| Predicate | votesForMonarchy |
P114455
|
FINISHED |
| Object | about 259563 |
—
|
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: about 259563 | Statement: [Norwegian referendum on monarchy, votesForMonarchy, about 259563]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votesForMonarchy Context triple: [Norwegian referendum on monarchy, votesForMonarchy, about 259563]
-
A.
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.
-
B.
keptMonarchyAfterReferendum
Indicates that, following a referendum on the political system, the country chose to retain the monarchy rather than abolish or replace it.
-
C.
monarchyStatus
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
-
D.
monarchist
chosen
Indicates support for or advocacy of a monarchical system of government or rule.
-
E.
monarchInQuestion
Indicates that the referenced entity is the specific monarch being discussed or evaluated in the given context.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.