Triple
T27114812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairey Delta 2 |
E686811
|
entity |
| Predicate | pilotOnRecordFlight |
P161865
|
FINISHED |
| Object | Peter Twiss |
—
|
NE NERFINISHED |
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: Peter Twiss | Statement: [Fairey Delta 2, pilotOnRecordFlight, Peter Twiss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilotOnRecordFlight Context triple: [Fairey Delta 2, pilotOnRecordFlight, Peter Twiss]
-
A.
operatorDuringRecordFlight
Indicates that an operator is responsible for or engaged in operating a system or vehicle during the time a particular flight is being recorded.
-
B.
recordPilot
Indicates that an entity documents or logs information about a pilot, such as their identity, status, or activities.
-
C.
flightRecord
Indicates a record of a specific flight event or journey, capturing details about its occurrence and characteristics.
-
D.
testPilotOnFirstFlight
Indicates that the person served as the test pilot during the inaugural flight of an aircraft or aerospace vehicle.
-
E.
pilotFor
Indicates that one entity serves as the pilot operating or navigating a vehicle, aircraft, or vessel on behalf of another entity (such as an organization, mission, or owner).
- F. None of above. chosen
Provenance (4 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f624059f7c8190b245dc53535a1ff2 |
completed | May 2, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 8:56 a.m.