Triple
T32114182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Dynamic Digital Sound |
E820193
|
entity |
| Predicate | firstMajorReleaseYear |
P51515
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Sony Dynamic Digital Sound, firstMajorReleaseYear, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorReleaseYear Context triple: [Sony Dynamic Digital Sound, firstMajorReleaseYear, 1993]
-
A.
firstMajorRunYear
Indicates the year in which something (such as an event, production, or operation) first began its major or primary run.
-
B.
firstMajorUseYear
Indicates the calendar year in which something was first put into major or primary use.
-
C.
firstVersionYear
chosen
Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
-
D.
firstMajorVersionBy
Indicates that one entity is the earliest or initial major version created or released by another entity.
-
E.
firstCommercialReleaseYear
Indicates the calendar year in which something (such as a product, work, or service) was first made commercially available to the public.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:28 a.m.