Triple
T17430335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungnam |
E423851
|
entity |
| Predicate | evacuationType |
P44550
|
FINISHED |
| Object | amphibious evacuation |
—
|
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: amphibious evacuation | Statement: [Hungnam, evacuationType, amphibious evacuation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evacuationType Context triple: [Hungnam, evacuationType, amphibious evacuation]
-
A.
evacuationMethod
chosen
Indicates the means or procedure by which people or objects are removed from a place of danger or risk.
-
B.
evacuationReason
Indicates the cause or justification for why an evacuation took place or was required.
-
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.
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.
-
E.
evacuationPoint
Indicates a location designated as the place where people should gather or be moved to during an evacuation.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e448ffb9c8819099fabfeebdc06883 |
completed | April 19, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.