Triple
T13715890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Ouja |
E328896
|
entity |
| Predicate | post2003Event |
P1664
|
FINISHED |
| Object | subject to raids by coalition and Iraqi forces |
—
|
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: subject to raids by coalition and Iraqi forces | Statement: [Al-Ouja, post2003Event, subject to raids by coalition and Iraqi forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: post2003Event Context triple: [Al-Ouja, post2003Event, subject to raids by coalition and Iraqi forces]
-
A.
publishedEvent
Indicates that an entity has formally released or made an event publicly available or announced.
-
B.
post2009Status
Indicates the status or condition of an entity specifically in the period after the year 2009.
-
C.
event
chosen
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
D.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
E.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd43973cf08190a417d0cca9dd314a |
completed | April 13, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.