Triple
T19998236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilovaisk |
E494250
|
entity |
| Predicate | eventResult |
P138285
|
FINISHED |
| Object | large Ukrainian military losses in 2014 encirclement |
—
|
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: large Ukrainian military losses in 2014 encirclement | Statement: [Ilovaisk, eventResult, large Ukrainian military losses in 2014 encirclement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventResult Context triple: [Ilovaisk, eventResult, large Ukrainian military losses in 2014 encirclement]
-
A.
sportsEventFinish
Indicates the outcome or completion status of a sports event, typically linking the event to its final result or placement of participants.
-
B.
eventStatus
Indicates the current state or phase of an event within its lifecycle (e.g., planned, ongoing, completed, or canceled).
-
C.
competitionResult
Indicates the outcome of a competitive event, specifying how participants placed or performed relative to one another.
-
D.
competitionEnd
Indicates that a competitive event or contest has concluded or reached its final state.
-
E.
eventWon
Indicates that an entity has achieved victory or first place in a specified event or competition.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe6827481909469129feb9aad91 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:32 p.m.