Triple
T1301155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing KC-46 Pegasus |
E27765
|
entity |
| Predicate | firstDelivery |
P19762
|
FINISHED |
| Object | January 2019 |
—
|
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: January 2019 | Statement: [Boeing KC-46 Pegasus, firstDelivery, January 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDelivery Context triple: [Boeing KC-46 Pegasus, firstDelivery, January 2019]
-
A.
peakDeliveryTime
Indicates the time period during which deliveries are expected to be at their highest volume or frequency.
-
B.
deliverySpeed
Indicates the rate or promptness with which an item, service, or information is delivered from a source to a recipient.
-
C.
deliveryStandard
Indicates the agreed level, method, or timeframe by which a delivery is to be carried out between parties.
-
D.
deliveryGuarantee
Indicates that one party commits to ensuring that an item, service, or outcome will be delivered under specified conditions or within a defined timeframe.
-
E.
deliveredAt
chosen
Indicates the specific time or location at which something (such as a message, product, or service) is delivered.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c1145c2481908adf22dfd6ce349b |
completed | March 1, 2026, 10:43 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.