Triple
T18957752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beechcraft Musketeer |
E463822
|
entity |
| Predicate | controlConfiguration |
P38398
|
FINISHED |
| Object | dual controls |
—
|
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: dual controls | Statement: [Beechcraft Musketeer, controlConfiguration, dual controls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlConfiguration Context triple: [Beechcraft Musketeer, controlConfiguration, dual controls]
-
A.
controlParameter
Indicates that one entity functions as a parameter that governs, tunes, or constrains the behavior or operation of another entity.
-
B.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
C.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
D.
controlDirection
Indicates that one entity exerts influence or guidance over the orientation, course, or movement direction of another entity.
-
E.
controlLayout
chosen
Indicates that one entity determines or manages the spatial or structural arrangement 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5cee8348190b6506b10aed6c58a |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon