Triple
T16578488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutan Voyager |
E402775
|
entity |
| Predicate | flightRefueling |
P51382
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Rutan Voyager, flightRefueling, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightRefueling Context triple: [Rutan Voyager, flightRefueling, none]
-
A.
refuellingSystem
chosen
Indicates a system or mechanism used to supply fuel from one entity to another.
-
B.
flightPhase
Indicates the specific stage or phase of an aircraft’s operation within a flight (e.g., taxi, takeoff, climb, cruise, descent, landing).
-
C.
flightEngineer
Indicates that one entity serves as a flight engineer for another entity (such as a mission, aircraft, or crew).
-
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.
flightMechanic
Indicates that one entity serves as a mechanic responsible for maintaining or repairing the aircraft associated with 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3595e9e1081909b220fb2de630348 |
completed | April 18, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.