Triple
T878861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grob G 120 |
E18980
|
entity |
| Predicate | typicalPilotPosition |
P21024
|
FINISHED |
| Object | left seat |
—
|
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: left seat | Statement: [Grob G 120, typicalPilotPosition, left seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPilotPosition Context triple: [Grob G 120, typicalPilotPosition, left seat]
-
A.
locationOnAircraft
Indicates that one entity is physically situated on or within an aircraft.
-
B.
pilotDirector
Indicates that one entity serves as the director of the pilot episode or initial installment of another entity (such as a series or project).
-
C.
cockpitType
Indicates the specific configuration or style of cockpit associated with an entity (e.g., vehicle or aircraft).
-
D.
departurePilot
Indicates that a pilot is responsible for operating or commanding the departing flight or vehicle.
-
E.
notablePilot
Indicates that an entity is a distinguished or noteworthy pilot associated with another entity (such as a vehicle, event, or organization).
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acb1dc20819095b9bb093158b60d |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:39 p.m.