Triple
T16568429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grdelica train bombing |
E402521
|
entity |
| Predicate | videoEvidence |
P83514
|
FINISHED |
| Object | cockpit video released by NATO |
—
|
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: cockpit video released by NATO | Statement: [Grdelica train bombing, videoEvidence, cockpit video released by NATO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoEvidence Context triple: [Grdelica train bombing, videoEvidence, cockpit video released by NATO]
-
A.
homeVideo
Indicates that an entity is a video recording made in a domestic or personal setting, typically by non-professionals for private use.
-
B.
videoReplayUsed
Indicates that a video replay was utilized to review or analyze a prior event or action.
-
C.
videoOutput
Indicates that one entity produces or provides video signals or content as output to another entity or medium.
-
D.
hasVideoRecording
chosen
Indicates that there exists an associated video recording capturing or documenting the referenced entity or event.
-
E.
musicVideoReference
Indicates that one entity is referenced, featured, or cited within the music video of another 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35773c00c819091731bebc02a69bb |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.