Triple
T1100531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of State (Norway) |
E24367
|
entity |
| Predicate | recordsDecisionsIn |
P13284
|
FINISHED |
| Object | protocols of the Council of State |
—
|
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: protocols of the Council of State | Statement: [Council of State (Norway), recordsDecisionsIn, protocols of the Council of State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsDecisionsIn Context triple: [Council of State (Norway), recordsDecisionsIn, protocols of the Council of State]
-
A.
reportsDecisionsOf
Indicates that one entity communicates or provides information about the decisions made by another entity.
-
B.
decisionsAre
Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
-
C.
documentsDecisionsOn
chosen
Indicates that one entity records, details, or formally captures the decisions made about another entity.
-
D.
reviewsDecisionsFrom
Indicates that one entity examines and evaluates the decisions made by another entity.
-
E.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9c079f48190a0e0ddda182f7a01 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b745ef3481909a7ce4647c8567b3 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.