Triple
T35281406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub Phatty |
E1018941
|
entity |
| Predicate | controlPanelType |
P198149
|
FINISHED |
| Object | knob-per-function style interface |
—
|
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: knob-per-function style interface | Statement: [Sub Phatty, controlPanelType, knob-per-function style interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlPanelType Context triple: [Sub Phatty, controlPanelType, knob-per-function style interface]
-
A.
controlsType
Indicates that one entity has authority over, or the ability to direct or regulate, the type or category of another entity.
-
B.
controlsDeviceType
Indicates that an entity has authority over or can operate a specific type or category of device.
-
C.
controlsServiceType
Indicates that one entity has authority to manage, regulate, or determine the operation or availability of a particular type of service.
-
D.
controlUnitType
Indicates the specific kind or category of control unit associated with or assigned to an entity.
-
E.
typeOfControl
Indicates the specific manner or mechanism by which one entity exercises control or influence over another.
- F. None of above. chosen
Provenance (4 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fecd091abc8190872974de731a80fa |
completed | May 9, 2026, 5:58 a.m. |
Created at: May 3, 2026, 4:03 p.m.