Triple
T37843111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article V of the Oklahoma Constitution |
E943528
|
entity |
| Predicate | dateOfOriginalEffect |
P196646
|
FINISHED |
| Object | 1907 |
—
|
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: 1907 | Statement: [Article V of the Oklahoma Constitution, dateOfOriginalEffect, 1907]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfOriginalEffect Context triple: [Article V of the Oklahoma Constitution, dateOfOriginalEffect, 1907]
-
A.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
B.
lessEffectiveAt
Indicates that one entity has a reduced ability or lower level of success in performing, influencing, or achieving a particular action or outcome compared to another.
-
C.
decisionEffectiveDate
Indicates the date on which a particular decision becomes valid, operative, or officially takes effect.
-
D.
dateEnacted
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
-
E.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69fe5ec84910819094cb15269ace7c51 |
completed | May 8, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:19 p.m.