Triple
T7325454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z-Wave |
E168859
|
entity |
| Predicate | canBeControlledBy |
P72492
|
FINISHED |
| Object | smart home hubs |
—
|
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: smart home hubs | Statement: [Z-Wave, canBeControlledBy, smart home hubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeControlledBy Context triple: [Z-Wave, canBeControlledBy, smart home hubs]
-
A.
rangeControlledBy
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
B.
oppositeControlledBy
Indicates that one entity is under the control or influence of another entity that is positioned or defined as its opposite or counterpart.
-
C.
operatesUnderControlOf
chosen
Indicates that one entity functions or carries out its activities subject to the authority, direction, or governance of another entity.
-
D.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
E.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f04993408190b73fb46d83a632d5 |
completed | March 27, 2026, 9:02 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:03 p.m.