Triple
T26748114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Aerial |
E674457
|
entity |
| Predicate | includesEvacuationOf |
P193991
|
FINISHED |
| Object | British troops |
—
|
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: British troops | Statement: [Operation Aerial, includesEvacuationOf, British troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEvacuationOf Context triple: [Operation Aerial, includesEvacuationOf, British troops]
-
A.
evacuatesFrom
Indicates that an entity leaves or is removed from a place or situation, typically due to danger or an emergency.
-
B.
evacuatedDuring
Indicates that one entity was removed or relocated from a place or situation during the time period or event represented by the other entity.
-
C.
hasEvacuationPlans
Indicates that an entity possesses or has established specific plans or procedures for evacuating people from a location in case of an emergency.
-
D.
numberOfEvacuated
Indicates the total count of individuals who have been evacuated from a location or situation.
-
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. chosen
Provenance (4 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: April 27, 2026, 3:52 a.m.