Triple
T18885039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Tigers |
E461935
|
entity |
| Predicate | firstKnownAttackContext |
P85993
|
FINISHED |
| Object | attack on Sri Lankan military targets |
—
|
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: attack on Sri Lankan military targets | Statement: [Black Tigers, firstKnownAttackContext, attack on Sri Lankan military targets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstKnownAttackContext Context triple: [Black Tigers, firstKnownAttackContext, attack on Sri Lankan military targets]
-
A.
attackContext
chosen
Indicates the situational circumstances, conditions, or factors surrounding an attack event or action.
-
B.
attackDate
Indicates the calendar date on which an attack or assault event took place.
-
C.
firstShotsFiredOn
Indicates that the referenced event or entity marks the initial occurrence of shots being fired on a specified date, time, or occasion.
-
D.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
E.
firstShotsFiredAt
Indicates the location or time at which the initial gunshots or opening fire in an incident occurred.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d53e608190b8740c092b6e1523 |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:57 a.m.