Triple
T22620608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CF6-80A |
E558265
|
entity |
| Predicate | engineControl |
P115681
|
FINISHED |
| Object | hydromechanical control system |
—
|
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: hydromechanical control system | Statement: [CF6-80A, engineControl, hydromechanical control system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineControl Context triple: [CF6-80A, engineControl, hydromechanical control system]
-
A.
operatesEngine
Indicates that one entity controls or uses an engine to make it function.
-
B.
engine
Indicates a relationship where something functions as, contains, or is driven by an engine as its source of mechanical power or propulsion.
-
C.
controlsSystem
chosen
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
D.
engineBase
Indicates that one entity serves as the foundational or primary engine upon which another engine or engine-related component is built or derived.
-
E.
engineComponent
Indicates that one entity functions as a component or part of an engine in relation 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e383b048190a432c540185916d0 |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3 p.m.