Triple
T29500228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ramadi (2015–2016) |
E748344
|
entity |
| Predicate | dateOfFullControlDeclared |
P160307
|
FINISHED |
| Object | 2016-02-09 |
—
|
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: 2016-02-09 | Statement: [Battle of Ramadi (2015–2016), dateOfFullControlDeclared, 2016-02-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFullControlDeclared Context triple: [Battle of Ramadi (2015–2016), dateOfFullControlDeclared, 2016-02-09]
-
A.
lastCheckedPartyControlDate
Indicates the date on which the party control status was most recently verified or updated.
-
B.
declaredDate
chosen
Indicates the date on which something is formally announced, proclaimed, or made official.
-
C.
fullContainmentDate
Indicates that one time period or date range is entirely contained within another, without extending beyond its start or end dates.
-
D.
declaredFullyOperationalBy
Indicates that one entity has officially stated that another entity is completely ready and capable of functioning as intended.
-
E.
complianceDate
Indicates the date on which an entity meets, satisfies, or becomes compliant with a specified requirement, rule, or standard.
- 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_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:22 p.m.