Triple
T23410124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio Constitution |
E560044
|
entity |
| Predicate | secondVersionAdopted |
P84426
|
FINISHED |
| Object | 1851 |
—
|
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: 1851 | Statement: [Ohio Constitution, secondVersionAdopted, 1851]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondVersionAdopted Context triple: [Ohio Constitution, secondVersionAdopted, 1851]
-
A.
secondVersion
chosen
Indicates that one entity is a later or updated second version of another entity.
-
B.
finalVersionAdopted
Indicates that a proposed item, document, or decision has completed all required processes and has been formally accepted as the definitive, authoritative version.
-
C.
previousVersionAdopted
Indicates that one entity has been adopted or implemented as a successor to an earlier version represented by the other entity.
-
D.
secondFullVersionReference
Indicates that an entity refers to a second complete or fully detailed version of another entity.
-
E.
secondedBy
Indicates that an initial proposal, motion, or action by one entity is formally supported or endorsed by another entity as a second.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a510b3848190ae42679ef0bcd424 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:38 p.m.