Triple
T7584565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Ariel |
E179573
|
entity |
| Predicate | evacuationMode |
P44550
|
FINISHED |
| Object | sea transport |
—
|
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: sea transport | Statement: [Operation Ariel, evacuationMode, sea transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evacuationMode Context triple: [Operation Ariel, evacuationMode, sea transport]
-
A.
evacuationMethod
chosen
Indicates the means or procedure by which people or objects are removed from a place of danger or risk.
-
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.
evacuationPoint
Indicates a location designated as the place where people should gather or be moved to during an evacuation.
-
D.
hasEvacuationZone
Indicates that a specified area or location falls within a designated evacuation zone associated with another entity (such as an event, hazard, or authority).
-
E.
numberOfEvacuated
Indicates the total count of individuals who have been evacuated from a location or situation.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f993cd0c8190864f801074625a32 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:52 p.m.