Triple
T26326924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qassam rockets |
E662276
|
entity |
| Predicate | firstUsedInConflict |
P51387
|
FINISHED |
| Object | Second Intifada |
—
|
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: Second Intifada | Statement: [Qassam rockets, firstUsedInConflict, Second Intifada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUsedInConflict Context triple: [Qassam rockets, firstUsedInConflict, Second Intifada]
-
A.
firstMajorUseConflict
chosen
Indicates the earliest significant conflict or dispute in which the entity was prominently used or involved.
-
B.
usedByDuringConflict
Indicates that one entity made practical use of another entity specifically in the context of a particular conflict or war.
-
C.
firstUsedAs
Indicates that one entity was the earliest or original thing in which another entity was used or applied.
-
D.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
E.
firstUsedBy
Indicates that something was initially utilized, applied, or employed by a particular entity before any others.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: April 26, 2026, 10:31 p.m.