Triple
T23225002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 North India floods |
E580989
|
entity |
| Predicate | peopleAffectedEstimate |
P54084
|
FINISHED |
| Object | hundreds of thousands |
—
|
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: hundreds of thousands | Statement: [2013 North India floods, peopleAffectedEstimate, hundreds of thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peopleAffectedEstimate Context triple: [2013 North India floods, peopleAffectedEstimate, hundreds of thousands]
-
A.
estimatedAffectedPeople
chosen
Indicates the estimated number of people expected to be impacted by a particular event, condition, or action.
-
B.
estimatedVictimsUpperBound
Indicates the maximum estimated number of victims associated with an event, incident, or situation.
-
C.
estimatedVictimsLowerBound
Indicates the minimum estimated number of victims associated with an event, entity, or incident.
-
D.
estimatedVictimsUnderAuthority
Indicates that a specified authority is estimated to have a certain number of victims under its control, influence, or jurisdiction.
-
E.
affectedPeople
Indicates the people who are impacted or influenced by a particular event, action, or condition.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922d30b08190a3c54bab58f5c8e7 |
completed | April 29, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.