Triple
T5651750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Code of 1687 |
E124526
|
entity |
| Predicate | inForceAfter |
P65434
|
FINISHED |
| Object | dissolution of Denmark-Norway in 1814 |
—
|
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: dissolution of Denmark-Norway in 1814 | Statement: [Norwegian Code of 1687, inForceAfter, dissolution of Denmark-Norway in 1814]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inForceAfter Context triple: [Norwegian Code of 1687, inForceAfter, dissolution of Denmark-Norway in 1814]
-
A.
inForceUntil
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
-
B.
inForceIn
Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
-
C.
inForce
Indicates that a rule, law, agreement, or condition is currently valid, active, and being applied or enforced.
-
D.
inForceSince
Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
-
E.
inForceStatus
Indicates that a rule, agreement, or condition is currently active, valid, and legally or formally in effect.
- F. None of above. chosen
Provenance (4 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022d6af9481909eaeead2a39525ce |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2274b48190b2ef57ed728f785c |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0727bc8190b16e9a669c04b4dd |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:42 p.m.