Triple
T24790544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YF-16 |
E620238
|
entity |
| Predicate | flightControlType |
P109258
|
FINISHED |
| Object | relaxed static stability |
—
|
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: relaxed static stability | Statement: [YF-16, flightControlType, relaxed static stability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightControlType Context triple: [YF-16, flightControlType, relaxed static stability]
-
A.
aircraftControlType
chosen
Indicates the type or method of control used to operate or direct an aircraft.
-
B.
crewControls
Indicates that a crew has authority over, manages, or directs the operation or behavior of another entity.
-
C.
controlsPhaseOfFlight
Indicates that one entity has authority over or manages a specific phase of another entity’s flight operation.
-
D.
attitudeControlMethod
Indicates the technique or mechanism used to control or adjust the orientation or pointing direction of an object (such as a vehicle or device).
-
E.
flightDeckFeature
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:47 a.m.