Triple
T1447884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazon Echo |
E31216
|
entity |
| Predicate | supportsInteractionMode |
P23418
|
FINISHED |
| Object | voice commands |
—
|
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: voice commands | Statement: [Amazon Echo, supportsInteractionMode, voice commands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInteractionMode Context triple: [Amazon Echo, supportsInteractionMode, voice commands]
-
A.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
B.
userInteractionModel
chosen
Indicates how a user is expected to interact with a system, defining the style, rules, or pattern of those interactions.
-
C.
supportsOperationsIn
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
-
D.
hasAccessMode
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
-
E.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55aa7dc8190aa7452d80ec8305e |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.