Triple
T38293323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby noise reduction family |
E1022420
|
entity |
| Predicate | commerciallySuccessful |
P191858
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dolby noise reduction family, commerciallySuccessful, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commerciallySuccessful Context triple: [Dolby noise reduction family, commerciallySuccessful, true]
-
A.
commercialSuccessIn
Indicates that something has achieved notable commercial success within a specified market, region, or domain.
-
B.
continuedCommercialSuccessFor
Indicates that an entity maintains its strong commercial performance or profitability over an extended period of time.
-
C.
commercialized
Indicates that something has been developed, marketed, or exploited for profit in a commercial context.
-
D.
commercializedIn
Indicates that something has been brought to market or made available for commercial sale or use within a specified place or context.
-
E.
commercialOutcome
Indicates that an action, event, or relationship results in, or is associated with, a specific commercial or financial consequence.
- F. None of above. chosen
Provenance (4 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.