Triple
T1182534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 23 of the Constitution of Norway |
E25169
|
entity |
| Predicate | isInForce |
P5570
|
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: [Article 23 of the Constitution of Norway, isInForce, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInForce Context triple: [Article 23 of the Constitution of Norway, isInForce, true]
-
A.
inForceStatus
Indicates that a rule, agreement, or condition is currently active, valid, and legally or formally in effect.
-
B.
inForceIn
Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
-
C.
inForceSince
Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
-
D.
inForceUntil
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
-
E.
inForce
chosen
Indicates that a rule, law, agreement, or condition is currently valid, active, and being applied or enforced.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd35fb888190adf1e5d0615fa725 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.