Triple
T16756065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Constitution of 1848 |
E407207
|
entity |
| Predicate | inForceFromYear |
P6161
|
FINISHED |
| Object | 1848 |
—
|
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: 1848 | Statement: [French Constitution of 1848, inForceFromYear, 1848]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inForceFromYear Context triple: [French Constitution of 1848, inForceFromYear, 1848]
-
A.
inForceIn
Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
-
B.
inForceInPeriod
Indicates that something (such as a rule, contract, or condition) is valid, applicable, or legally effective during a specified time period.
-
C.
cameIntoForceInYear
chosen
Indicates that a law, agreement, or formal measure became legally effective or operational in a specified calendar year.
-
D.
inForce
Indicates that a rule, law, agreement, or condition is currently valid, active, and being applied or enforced.
-
E.
inForceSince
Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abe831ec8190bac05b07db6153c1 |
completed | April 18, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.