Triple
T5876952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K9A2 |
E130648
|
entity |
| Predicate | hasControlInterface |
P22670
|
FINISHED |
| Object | digital control panels |
—
|
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: digital control panels | Statement: [K9A2, hasControlInterface, digital control panels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlInterface Context triple: [K9A2, hasControlInterface, digital control panels]
-
A.
hasCommunicationInterface
Indicates that one entity provides or supports a specific means or channel through which it can communicate or exchange data with another entity or system.
-
B.
hasControlCab
Indicates that an entity is equipped with or includes a control cab used for operating or controlling it.
-
C.
hasControlElement
Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
-
D.
hasTouchControls
chosen
Indicates that an entity supports or is operated through touch-based input controls.
-
E.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.