Triple
T23225001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 North India floods |
E580989
|
entity |
| Predicate | peopleMissingEstimate |
P87238
|
FINISHED |
| Object | 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: thousands | Statement: [2013 North India floods, peopleMissingEstimate, thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peopleMissingEstimate Context triple: [2013 North India floods, peopleMissingEstimate, thousands]
-
A.
missingPersonsEstimate
chosen
Indicates an estimated number of people who are unaccounted for or reported missing in a given context or event.
-
B.
populationEstimateLoss
Indicates a reduction or decrease in a previously estimated population size.
-
C.
hasApproximateNumberOfPeople
Indicates that an entity is associated with an estimated or approximate count of people, rather than an exact number.
-
D.
estimatedAffectedPeople
Indicates the estimated number of people expected to be impacted by a particular event, condition, or action.
-
E.
estimatedMemberCount
Indicates the approximate or predicted number of members associated with an entity.
- 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.