Triple
T2849617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby A-type noise reduction |
E63060
|
entity |
| Predicate | introducedYearApproximate |
P13193
|
FINISHED |
| Object | 1965 |
—
|
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: 1965 | Statement: [Dolby A-type noise reduction, introducedYearApproximate, 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedYearApproximate Context triple: [Dolby A-type noise reduction, introducedYearApproximate, 1965]
-
A.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
B.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
-
C.
brandLaunchYear
Indicates the calendar year in which a brand was first introduced or launched to the market.
-
D.
incorporationYear
Indicates the calendar year in which an organization or entity was formally incorporated or legally established.
-
E.
approximateStartYear
chosen
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf41ac24819087c5b72e3b84117c |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.