Triple
T17022441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1809 Instrument of Government |
E412978
|
entity |
| Predicate | inForceTo |
P2110
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [1809 Instrument of Government, inForceTo, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inForceTo Context triple: [1809 Instrument of Government, inForceTo, 1974]
-
A.
inForceIn
Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
-
B.
inForce
Indicates that a rule, law, agreement, or condition is currently valid, active, and being applied or enforced.
-
C.
inForceUntil
chosen
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
-
D.
inForceAfter
Indicates that a condition, rule, or agreement becomes valid or operative only after a specified time, event, or state has occurred.
-
E.
inForceInPart
Indicates that a rule, agreement, or provision is currently effective only for some of its parts, conditions, or scope, but not in its entirety.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d1d2e48190bbcba129247c6c2e |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.