Triple
T16568413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grdelica train bombing |
E402521
|
entity |
| Predicate | objectHit |
P110638
|
FINISHED |
| Object | passenger train |
—
|
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: passenger train | Statement: [Grdelica train bombing, objectHit, passenger train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectHit Context triple: [Grdelica train bombing, objectHit, passenger train]
-
A.
typeOfHit
Indicates the specific category or kind of hit or strike that occurred in an interaction or event.
-
B.
playedOnHit
Indicates that an entity performed or participated in a play or action that resulted in a hit.
-
C.
hitSingle
Indicates that a batter successfully hits the ball and reaches first base safely, recording a single.
-
D.
objet
chosen
Indicates that one entity is the object (recipient or target) of an action or relation performed by another entity.
-
E.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
- 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.