Triple
T20322375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Ghouta |
E492235
|
entity |
| Predicate | reportedAgentInAttack |
P139677
|
FINISHED |
| Object | sarin |
—
|
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: sarin | Statement: [Eastern Ghouta, reportedAgentInAttack, sarin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedAgentInAttack Context triple: [Eastern Ghouta, reportedAgentInAttack, sarin]
-
A.
attackOccurred
Indicates that an act of aggression or violence was carried out by one party against another.
-
B.
reportedAs
Indicates that one entity has been formally reported or flagged to another entity, typically as problematic, suspicious, or noteworthy.
-
C.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
D.
officeAttacked
Indicates that an office was the target of an attack or violent action.
-
E.
reportedFor
Indicates that one entity has formally notified an authority or system about another entity’s behavior, condition, or status, typically to trigger review or action.
- F. None of above. chosen
Provenance (4 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778c4430819083b17da5067b88ef |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:20 a.m.