Triple
T19452218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonos, Inc. |
E486639
|
entity |
| Predicate | stockTicker |
P1447
|
FINISHED |
| Object | SONO |
—
|
NE NERFINISHED |
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: SONO | Statement: [Sonos, Inc., stockTicker, SONO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SONO Context triple: [Sonos, Inc., stockTicker, SONO]
-
A.
SONO
chosen
SONO is the stock ticker symbol for Sonos, Inc., a company known for its wireless home audio and smart speaker systems.
-
B.
SON
SON is the commonly used acronym for the Saugeen Ojibway Nation, an Indigenous community in Ontario composed primarily of the Saugeen First Nation and the Chippewas of Nawash Unceded First Nation.
-
C.
SON
SON is the vehicle registration code assigned to the Sonneberg district in the German state of Thuringia.
-
D.
S0N
S0N is a Canadian postal code prefix used for addresses in and around Shaunavon, Saskatchewan.
-
E.
Sone
Sone is a Japanese surname borne by various notable figures in politics, arts, and sports.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63392aab08190aab09b7c356e5b10 |
completed | April 20, 2026, 2:09 p.m. |
Created at: April 10, 2026, 1:38 p.m.