Triple
T23225023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 North India floods |
E580989
|
entity |
| Predicate | evacuatedPeopleEstimate |
P8973
|
FINISHED |
| Object | over 100,000 people |
—
|
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: over 100,000 people | Statement: [2013 North India floods, evacuatedPeopleEstimate, over 100,000 people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evacuatedPeopleEstimate Context triple: [2013 North India floods, evacuatedPeopleEstimate, over 100,000 people]
-
A.
numberOfEvacuated
chosen
Indicates the total count of individuals who have been evacuated from a location or situation.
-
B.
populationBeforeEvacuation
Indicates the number of individuals present in a specified place or group prior to an evacuation event.
-
C.
numberOfEvacuatedSettlements
Indicates the total count of settlements that have been evacuated.
-
D.
numberOfTroopsEvacuated
Indicates the quantity of troops that have been removed from a location or situation and transported to safety.
-
E.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
- 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.