Triple
T5602149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeke |
E147143
|
entity |
| Predicate | referredAircraftLandingGear |
P3545
|
FINISHED |
| Object | retractable landing gear |
—
|
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: retractable landing gear | Statement: [Zeke, referredAircraftLandingGear, retractable landing gear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referredAircraftLandingGear Context triple: [Zeke, referredAircraftLandingGear, retractable landing gear]
-
A.
landingGear
Indicates that an entity’s landing gear is present, deployed, or otherwise involved in a landing-related state or action relative to another entity or context.
-
B.
landingGearType
chosen
Indicates the specific kind or configuration of landing gear that an object (typically an aircraft or vehicle) uses.
-
C.
numberOfMainLandingGearLegs
Indicates the count of main landing gear legs that an aircraft has.
-
D.
typeOfLanding
Indicates the specific kind or category of landing that occurs in a given event or situation.
-
E.
notableGroundEquipment
Indicates that there is ground-based equipment at or associated with an entity that is considered significant or noteworthy in some context.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020dbd6dc8190ba011876c205754e |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.