Triple
T887274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Vittles |
E19157
|
entity |
| Predicate | dailySorties |
P21427
|
FINISHED |
| Object | over 1,000 flights per day at peak |
—
|
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: over 1,000 flights per day at peak | Statement: [Operation Vittles, dailySorties, over 1,000 flights per day at peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dailySorties Context triple: [Operation Vittles, dailySorties, over 1,000 flights per day at peak]
-
A.
notableAirOperation
Indicates that there is a significant or historically important air operation associated with the subject.
-
B.
aircraftFlown
Indicates that an entity (typically a person or organization) operates or pilots a particular aircraft.
-
C.
launchedAircraftIn
Indicates that an entity initiated the takeoff or deployment of an aircraft within a specified location or context.
-
D.
hasScheduledFlights
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
-
E.
lastFlight
Indicates that one flight is the final or most recent flight taken or operated by a given entity within a specified context or sequence.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ae787bf081909533082ca013624a |
completed | March 1, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8ff8c48190a33b00acf65c1276 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ae774fac8190b3134d64086d65fe |
completed | March 1, 2026, 9:24 p.m. |
Created at: March 1, 2026, 7:39 p.m.