Triple
T33377054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leavenworth, Indiana |
E854661
|
entity |
| Predicate | replattedAfterEvent |
P194484
|
FINISHED |
| Object | 1937 Ohio River flood |
—
|
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: 1937 Ohio River flood | Statement: [Leavenworth, Indiana, replattedAfterEvent, 1937 Ohio River flood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replattedAfterEvent Context triple: [Leavenworth, Indiana, replattedAfterEvent, 1937 Ohio River flood]
-
A.
replacedAfterEvent
Indicates that one entity takes the place of another entity following a specified event or occurrence.
-
B.
rebuiltAfterEvent
Indicates that an entity was reconstructed or restored following a specific event that caused damage, destruction, or significant alteration.
-
C.
renamedAfterEvent
Indicates that an entity has changed its name as a consequence of, or in commemoration of, a specific event.
-
D.
changesAfterEvents
Indicates that one entity undergoes a change as a consequence of, or following, the occurrence of specified events.
-
E.
repealedAfterEvent
Indicates that a law or regulation was repealed as a consequence of, or following, a specific event.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69fd76d0d7608190b350336d6c18182d |
completed | May 8, 2026, 5:38 a.m. |
Created at: May 1, 2026, 1:35 a.m.