Triple
T23401242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumiyah |
E559508
|
entity |
| Predicate | advocatesTactic |
P1716
|
FINISHED |
| Object | stabbings |
—
|
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: stabbings | Statement: [Rumiyah, advocatesTactic, stabbings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advocatesTactic Context triple: [Rumiyah, advocatesTactic, stabbings]
-
A.
tactic
chosen
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
B.
advocates
Indicates that one entity publicly supports, recommends, or argues in favor of another entity or its interests.
-
C.
advocatesIn
Indicates that an entity actively supports, promotes, or argues in favor of something within a particular context, domain, or setting.
-
D.
parliamentarianTactic
Indicates the use of procedural or strategic maneuvers within a parliamentary or legislative setting to influence debate, decision-making, or outcomes.
-
E.
advocatesAgainst
Indicates that one entity actively opposes, argues against, or campaigns to prevent or stop another entity, action, or idea.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4dfa4c881908df0eced4855c0d9 |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:37 p.m.