Triple
T32922765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri Executive Order 44 |
E842187
|
entity |
| Predicate | dateRescinded |
P175399
|
FINISHED |
| Object | 1976-06-25 |
—
|
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: 1976-06-25 | Statement: [Missouri Executive Order 44, dateRescinded, 1976-06-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRescinded Context triple: [Missouri Executive Order 44, dateRescinded, 1976-06-25]
-
A.
dismissalDate
Indicates the date on which an entity (such as a person, case, or employment) is formally dismissed, terminated, or ended.
-
B.
repudiatedOn
Indicates the specific date or time at which something (such as a claim, agreement, or association) was formally rejected, disowned, or renounced.
-
C.
rescissionPeriod
Indicates the time span during which a party is allowed to cancel or revoke an agreement or transaction without penalty.
-
D.
repudiatedAfter
Indicates that one entity formally rejects, disavows, or withdraws support for another entity after a specified time or subsequent event.
-
E.
suspensionDate
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: May 1, 2026, 1:20 a.m.