Triple
T6725460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Hannibal |
E153504
|
entity |
| Predicate | estimatedNumberOfEvacuees |
P8973
|
FINISHED |
| Object | over 1,000,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 1,000,000 | Statement: [Operation Hannibal, estimatedNumberOfEvacuees, over 1,000,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedNumberOfEvacuees Context triple: [Operation Hannibal, estimatedNumberOfEvacuees, over 1,000,000]
-
A.
numberOfEvacuated
chosen
Indicates the total count of individuals who have been evacuated from a location or situation.
-
B.
numberOfTroopsEvacuated
Indicates the quantity of troops that have been removed from a location or situation and transported to safety.
-
C.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
D.
numberOfEvacuatedTonsOfCargo
Indicates the quantity of cargo, measured in tons, that has been evacuated from a location or situation.
-
E.
estimatedNumberOfPeopleSaved
Indicates the approximate count of individuals whose lives were preserved or harm was averted as a result of a particular action, intervention, or 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:08 p.m.