Triple
T30239596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CV-22 Osprey |
E768871
|
entity |
| Predicate | rangeWithAerialRefueling |
P124460
|
FINISHED |
| Object | extended to transcontinental distances |
—
|
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: extended to transcontinental distances | Statement: [CV-22 Osprey, rangeWithAerialRefueling, extended to transcontinental distances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeWithAerialRefueling Context triple: [CV-22 Osprey, rangeWithAerialRefueling, extended to transcontinental distances]
-
A.
usedAerialRefueling
Indicates that one entity received fuel in flight from another entity via aerial refueling.
-
B.
canBeAerialRefueled
chosen
Indicates that one entity has the capability to receive fuel from another entity while in flight through aerial refueling operations.
-
C.
airRefuellingMethod
Indicates the method or technique used to transfer fuel between aircraft during in-flight refuelling.
-
D.
aircraftTanker
Indicates that one aircraft is serving as an aerial refueling tanker for another aircraft.
-
E.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6804ea5148190a2b99a016b1644f5 |
completed | May 2, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:38 p.m.