Triple
T3747577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FADEC |
E81243
|
entity |
| Predicate | interfacesWith |
P12981
|
FINISHED |
| Object | cockpit throttle 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: cockpit throttle controls | Statement: [FADEC, interfacesWith, cockpit throttle controls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interfacesWith Context triple: [FADEC, interfacesWith, cockpit throttle controls]
-
A.
interoperabilityWith
Indicates that one system, component, or standard can effectively exchange and use information or services with another.
-
B.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
C.
interfaceLocation
Indicates the spatial or logical position where two systems, components, or entities meet and interact.
-
D.
alsoImplements
Indicates that an entity, in addition to its primary implementation, implements another interface, protocol, or specification as well.
-
E.
hasInterface
chosen
Indicates that one entity provides, exposes, or is connected through a defined interface to 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb6ac5ac8190934ec1a6c887a8f5 |
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.