Triple
T4622737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebraska Legislature |
E101023
|
entity |
| Predicate | reformApprovedByVotersIn |
P4888
|
FINISHED |
| Object | 1934 |
—
|
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: 1934 | Statement: [Nebraska Legislature, reformApprovedByVotersIn, 1934]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformApprovedByVotersIn Context triple: [Nebraska Legislature, reformApprovedByVotersIn, 1934]
-
A.
subjectToReformBy
Indicates that an entity is undergoing or designated for changes, improvements, or restructuring carried out by another entity.
-
B.
referendumResultImplemented
Indicates that the outcome of a referendum has been put into effect through concrete actions or legal/administrative measures.
-
C.
reform
chosen
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
D.
implementedReformsIn
Indicates that an entity (typically a person, organization, or government) carried out or put into effect specific reforms within a particular context, domain, or location.
-
E.
proposalApprovedByCongressOn
Indicates that a specific proposal received formal approval from a legislative body (Congress) on a particular date.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a053d38819097b3ecbc06aa6e4d |
completed | March 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.