Triple
T20331720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonos Arc |
E492498
|
entity |
| Predicate | hasDriverConfiguration |
P13644
|
FINISHED |
| Object | up‑firing drivers |
—
|
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: up‑firing drivers | Statement: [Sonos Arc, hasDriverConfiguration, up‑firing drivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDriverConfiguration Context triple: [Sonos Arc, hasDriverConfiguration, up‑firing drivers]
-
A.
hasDriver
Indicates that an entity is operated, controlled, or driven by a specific person or agent.
-
B.
hasConfiguration
chosen
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
C.
hasNotableDriver
Indicates that an entity is associated with a driver who is notable or distinguished in some recognized way.
-
D.
hasDevelopmentDriver
Indicates that one entity serves as a driving factor, cause, or motivator for the development, growth, or advancement of another entity.
-
E.
hasCarConfiguration
Indicates that an entity is associated with a specific car configuration, detailing how the car is set up or specified.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e7baf481909282293d78597634 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:22 a.m.