Triple
T3751973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fokker Universal |
E81352
|
entity |
| Predicate | landingGearOptions |
P3545
|
FINISHED |
| Object | wheels |
—
|
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: wheels | Statement: [Fokker Universal, landingGearOptions, wheels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingGearOptions Context triple: [Fokker Universal, landingGearOptions, wheels]
-
A.
landingGearType
chosen
Indicates the specific kind or configuration of landing gear that an object (typically an aircraft or vehicle) uses.
-
B.
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.
-
C.
landingCapability
Indicates the ability or suitability of an entity (e.g., a vehicle or system) to perform a landing under specified conditions.
-
D.
wingConfiguration
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
-
E.
airSupport
Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb92135c819093f6d616d3ad28ff |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.