Triple
T497224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby Stereo |
E10319
|
entity |
| Predicate | SVAExpansion |
P8787
|
FINISHED |
| Object | Stereo Variable-Area |
—
|
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: Stereo Variable-Area | Statement: [Dolby Stereo, SVAExpansion, Stereo Variable-Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SVAExpansion Context triple: [Dolby Stereo, SVAExpansion, Stereo Variable-Area]
-
A.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
B.
expandsIn
chosen
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
C.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
D.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
E.
expansionSlots
Indicates that an entity provides one or more hardware expansion slots available for adding additional components or capabilities.
- 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.