Triple
T23085445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omega K-707 tanker |
E575583
|
entity |
| Predicate | fuelTransferCapability |
P140289
|
FINISHED |
| Object | air-to-air 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: air-to-air refueling | Statement: [Omega K-707 tanker, fuelTransferCapability, air-to-air refueling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelTransferCapability Context triple: [Omega K-707 tanker, fuelTransferCapability, air-to-air refueling]
-
A.
fuelTransferMethod
chosen
Indicates the method or process by which fuel is transferred from one entity or system to another.
-
B.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
C.
fuelTransferLocation
Indicates the place or facility where fuel is transferred from one container, vehicle, or system to another.
-
D.
fuelSystemFeature
Indicates that there is a specific characteristic, component, or functional aspect associated with a fuel system.
-
E.
fuelTypeSupported
Indicates that a system, device, or component is capable of operating with or is designed to accept a specified type of fuel.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da573588190a8e0c859667e64a6 |
completed | April 29, 2026, 4:48 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:57 p.m.