Triple
T1192302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of State (Norway) |
E25387
|
entity |
| Predicate | styleOfActs |
P15836
|
FINISHED |
| Object | in the name of the King in Council |
—
|
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: in the name of the King in Council | Statement: [Council of State (Norway), styleOfActs, in the name of the King in Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfActs Context triple: [Council of State (Norway), styleOfActs, in the name of the King in Council]
-
A.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
-
B.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
C.
styleInFull
chosen
Indicates that something is presented, written, or expressed in its complete, unabbreviated, or fully detailed form.
-
D.
styleOfJudges
Indicates the characteristic manner or approach that judges use when performing their judging role.
-
E.
performanceStyle
Indicates the manner or style in which an action, work, or performance is carried out or presented.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd761ef08190b431b80f326d1ab2 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.