Triple
T497228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby Stereo |
E10319
|
entity |
| Predicate | eraOfWidespreadUse |
P3656
|
FINISHED |
| Object | late 1970s |
—
|
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: late 1970s | Statement: [Dolby Stereo, eraOfWidespreadUse, late 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfWidespreadUse Context triple: [Dolby Stereo, eraOfWidespreadUse, late 1970s]
-
A.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
B.
popularizedIn
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
C.
historicalPeriodOfUse
chosen
Indicates the time period during which something was in active use or commonly utilized.
-
D.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
E.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f116f1b4819082f88d6c747368ae |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edfa87cc8190a77c726a5a55b7d9 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.