Triple
T32673241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Mississippi Flood of 1927 |
E835353
|
entity |
| Predicate | statesAffected |
P173249
|
FINISHED |
| Object | 7 U.S. states |
—
|
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: 7 U.S. states | Statement: [Great Mississippi Flood of 1927, statesAffected, 7 U.S. states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statesAffected Context triple: [Great Mississippi Flood of 1927, statesAffected, 7 U.S. states]
-
A.
affectedU.S.State
Indicates that a particular U.S. state is impacted or influenced by a specified event, condition, or entity.
-
B.
states
Indicates that an entity formally declares, expresses, or asserts a fact, opinion, or condition about another entity or situation.
-
C.
impactOnStates
chosen
Indicates the effect or influence that one entity, event, or condition has on the status, condition, or behavior of one or more states.
-
D.
affectedProvince
Indicates that a particular province is impacted or influenced by a specified event, action, or condition.
-
E.
stateSpecific
Indicates that the relationship, condition, or rule applies only within a particular state or region, and not universally.
- 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_69f3493134b48190aa3c8cb523bd3800 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 1, 2026, 1:09 a.m.