Triple
T3052297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyclone Tracy |
E60397
|
entity |
| Predicate | populationEvacuated |
P8973
|
FINISHED |
| Object | over 30,000 |
—
|
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 30,000 | Statement: [Cyclone Tracy, populationEvacuated, over 30,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationEvacuated Context triple: [Cyclone Tracy, populationEvacuated, over 30,000]
-
A.
numberOfEvacuated
chosen
Indicates the total count of individuals who have been evacuated from a location or situation.
-
B.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
C.
notableEvacuation
Indicates a significant, widely recognized instance of people being moved or fleeing from a place for safety, typically due to danger or emergency conditions.
-
D.
displacedPeopleEstimate
Indicates an estimated number of people who have been forced to leave their homes or usual places of residence due to a particular event or situation.
-
E.
estimatedEmigrants
Indicates the estimated number of people who have left a place or country to live elsewhere.
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9bf3c52c8190bbe8e5cb98c21715 |
completed | March 8, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.