Triple
T34728796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azovstal Iron and Steel Works |
E1001146
|
entity |
| Predicate | evacuationCoordinatedBy |
P129743
|
FINISHED |
| Object | United Nations |
—
|
NE NERFINISHED |
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: United Nations | Statement: [Azovstal Iron and Steel Works, evacuationCoordinatedBy, United Nations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evacuationCoordinatedBy Context triple: [Azovstal Iron and Steel Works, evacuationCoordinatedBy, United Nations]
-
A.
evacuationOrderIssuedBy
Indicates that a specific authority or organization has formally issued an evacuation order for people to leave a particular area.
-
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.
evacuationMethod
Indicates the means or procedure by which people or objects are removed from a place of danger or risk.
-
E.
evacuationCompletedBy
chosen
Indicates that the completion of an evacuation process is carried out or achieved by a specific agent 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.