Triple
T35088358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gouge flap high-lift device |
E1012640
|
entity |
| Predicate | operatingPosition |
P5131
|
FINISHED |
| Object | retracted in cruise |
—
|
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: retracted in cruise | Statement: [Gouge flap high-lift device, operatingPosition, retracted in cruise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingPosition Context triple: [Gouge flap high-lift device, operatingPosition, retracted in cruise]
-
A.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
B.
controlPosition
Indicates that one entity determines, directs, or regulates the spatial or organizational placement of another entity.
-
C.
positionA
chosen
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
D.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
E.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a012594c27081908c80f0e0e6010290 |
completed | May 11, 2026, 12:40 a.m. |
| PD | Predicate disambiguation | batch_6a01252350548190b1df9edc9e581e91 |
completed | May 11, 2026, 12:38 a.m. |
Created at: May 3, 2026, 4:01 p.m.