Triple
T11346477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HH-60 Pave Hawk |
E268727
|
entity |
| Predicate | inFlightRefuelingCapability |
P7141
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [HH-60 Pave Hawk, inFlightRefuelingCapability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inFlightRefuelingCapability Context triple: [HH-60 Pave Hawk, inFlightRefuelingCapability, yes]
-
A.
hasRefuellingCapabilityFor
chosen
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
B.
airRefuellingMethod
Indicates the method or technique used to transfer fuel between aircraft during in-flight refuelling.
-
C.
refuellingSystem
Indicates a system or mechanism used to supply fuel from one entity to another.
-
D.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
-
E.
hasFuelStorage
Indicates that one entity possesses or is equipped with a facility, container, or system used to store fuel for later 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e6f8aeb4819080476f16a69b2ee3 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.