Triple
T22620529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing E-4 |
E558263
|
entity |
| Predicate | missionEndurance |
P14979
|
FINISHED |
| Object | up to several days with aerial refueling |
—
|
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: up to several days with aerial refueling | Statement: [Boeing E-4, missionEndurance, up to several days with aerial refueling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionEndurance Context triple: [Boeing E-4, missionEndurance, up to several days with aerial refueling]
-
A.
missionDuration
Indicates the length of time over which a mission or operation takes place from start to finish.
-
B.
missionDurationCapability
chosen
Indicates the length of time an entity is capable of sustaining or performing a mission or operation.
-
C.
missionDurationPlanned
Indicates the length of time that a mission is scheduled or intended to last according to its plan.
-
D.
missionDurationType
Indicates the classification of a mission’s length or time span (e.g., short-term, long-term, extended).
-
E.
timeOfMission
Indicates the specific time or period during which a mission takes place or is scheduled.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e383b048190a432c540185916d0 |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3 p.m.