Triple
T29500227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ramadi (2015–2016) |
E748344
|
entity |
| Predicate | dateOfCityCenterRecapture |
P56190
|
FINISHED |
| Object | 2015-12-28 |
—
|
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: 2015-12-28 | Statement: [Battle of Ramadi (2015–2016), dateOfCityCenterRecapture, 2015-12-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfCityCenterRecapture Context triple: [Battle of Ramadi (2015–2016), dateOfCityCenterRecapture, 2015-12-28]
-
A.
cityRecapturedFrom
Indicates that control of a city has been regained by one party from another party that previously held it.
-
B.
dateOfCityCapture
Indicates the specific date on which a city was taken or captured, typically in a military or political context.
-
C.
recaptureDate
chosen
Indicates the date on which something that was previously captured or held is captured or taken back again.
-
D.
dateOfCityEncirclement
Indicates the date on which a city became fully encircled, typically by military or blockade forces, cutting it off from external access.
-
E.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 28, 2026, 4:22 p.m.