Triple
T9251808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sirte (2016) |
E222342
|
entity |
| Predicate | airSupportEndDate |
P6269
|
FINISHED |
| Object | 2016-12-19 |
—
|
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-12-19 | Statement: [Battle of Sirte (2016), airSupportEndDate, 2016-12-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airSupportEndDate Context triple: [Battle of Sirte (2016), airSupportEndDate, 2016-12-19]
-
A.
extendedSupportEndDate
Indicates the date on which an extended support period for something ends.
-
B.
notableFlightEndDate
Indicates the date on which a notable or significant flight concluded or reached its endpoint.
-
C.
airSupport
chosen
Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
-
D.
airSupportPlannedFrom
Indicates that air support operations are scheduled or intended to be provided starting from a specified source or location.
-
E.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
- 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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd05fb1454819098f452846ca4ca61 |
completed | April 1, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:31 p.m.