Triple
T3986812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby TrueHD |
E86890
|
entity |
| Predicate | decodingLocation |
P53677
|
FINISHED |
| Object | AV receiver |
—
|
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: AV receiver | Statement: [Dolby TrueHD, decodingLocation, AV receiver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decodingLocation Context triple: [Dolby TrueHD, decodingLocation, AV receiver]
-
A.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
B.
labelLocation
Indicates that a label or identifier is associated with a specific spatial or geographic location.
-
C.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
D.
eraLocation
Indicates the place or geographic context in which a particular historical era or time period occurs or is primarily associated.
-
E.
apseLocation
Indicates the specific place or position where an apse is situated within a larger structure or context.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefb7f92348190ae35f1d75b0b5d4f |
completed | March 9, 2026, 4:55 p.m. |
Created at: March 9, 2026, 3:33 p.m.