Triple
T20069934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-4B National Airborne Operations Center fleet |
E499705
|
entity |
| Predicate | canRefuelInFlight |
P124460
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [E-4B National Airborne Operations Center fleet, canRefuelInFlight, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canRefuelInFlight Context triple: [E-4B National Airborne Operations Center fleet, canRefuelInFlight, true]
-
A.
canBeAerialRefueled
chosen
Indicates that one entity has the capability to receive fuel from another entity while in flight through aerial refueling operations.
-
B.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
C.
fuelCondition
Indicates the state or quality of fuel associated with an entity, such as its level, usability, or readiness for operation.
-
D.
airSupport
Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
-
E.
hasFuel
Indicates that an entity possesses or contains fuel available for use.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e664365ad0819089103b00d1cf8c9f |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:39 p.m.