Triple
T8225987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Brussels bombings |
E192172
|
entity |
| Predicate | victimsNationalities |
P17603
|
FINISHED |
| Object | multiple countries |
—
|
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: multiple countries | Statement: [2016 Brussels bombings, victimsNationalities, multiple countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimsNationalities Context triple: [2016 Brussels bombings, victimsNationalities, multiple countries]
-
A.
hasVictimNationalities
chosen
Indicates that an event, incident, or action involved victims belonging to one or more specified nationalities.
-
B.
languageOfVictims
Indicates the language or languages spoken or used by the victims involved in an event or situation.
-
C.
legalStatusOfVictims
Indicates the legal classification or condition of the victims in relation to the event or action described.
-
D.
mainVictims
Indicates that the related entities are the primary or principal targets harmed or affected by an action, event, or perpetrator.
-
E.
perpetratorNationality
Indicates the country or nationality to which a perpetrator of an act, crime, or harmful event belongs.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb77fc10f48190b7e241c89885a478 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:45 p.m.