Triple
T21614855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma Organic Act |
E533407
|
entity |
| Predicate | hasLegalEffectFrom |
P27870
|
FINISHED |
| Object | 1890-05-02 |
—
|
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: 1890-05-02 | Statement: [Oklahoma Organic Act, hasLegalEffectFrom, 1890-05-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalEffectFrom Context triple: [Oklahoma Organic Act, hasLegalEffectFrom, 1890-05-02]
-
A.
hasLegalEffect
Indicates that an action, document, or condition produces recognized legal consequences or enforceable rights and obligations.
-
B.
hasLegalForceFrom
chosen
Indicates that one legal instrument, decision, or norm derives its binding legal effect or enforceability from another specified source.
-
C.
hasLegalEffectToday
Indicates that a legal rule, document, or status is currently in force and produces legal consequences as of today.
-
D.
hasLegalForceAs
Indicates that one thing possesses the binding legal effect or validity in the capacity or role of another specified thing.
-
E.
hasLegalForceIn
Indicates that something (such as a law, regulation, or agreement) is legally valid, binding, and enforceable within a specified jurisdiction or context.
- 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3ba9aca48190b5180eefd61a9fdc |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.