Triple
T24583092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 Kampala bombings |
E608305
|
entity |
| Predicate | targetedEvent |
P83867
|
FINISHED |
| Object | 2010 FIFA World Cup Final |
—
|
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: 2010 FIFA World Cup Final | Statement: [2010 Kampala bombings, targetedEvent, 2010 FIFA World Cup Final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedEvent Context triple: [2010 Kampala bombings, targetedEvent, 2010 FIFA World Cup Final]
-
A.
eventTarget
chosen
Indicates that an event is directed toward, affects, or is intended for a particular target entity.
-
B.
selectedEvent
Indicates that a particular event has been chosen or designated from a set of possible events.
-
C.
targetedActivity
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
D.
captureEvent
Indicates an event in which one entity successfully takes control, possession, or custody of another entity.
-
E.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a984577881908c855f5e05756909 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.