Triple
T12935186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby S |
E309488
|
entity |
| Predicate | manufacturerLicense |
P45762
|
FINISHED |
| Object | licensed technology |
—
|
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: licensed technology | Statement: [Dolby S, manufacturerLicense, licensed technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manufacturerLicense Context triple: [Dolby S, manufacturerLicense, licensed technology]
-
A.
licenseManufacturerOf
Indicates that one entity is authorized, via a license, to manufacture products or goods on behalf of or under the rights of another entity.
-
B.
licenseFor
Indicates that one entity grants or holds formal permission or authorization for another entity to perform an activity, use a resource, or operate under specified conditions.
-
C.
licenseProduction
chosen
Indicates that one party is authorized to manufacture or produce something under a license granted by another party.
-
D.
licenseModel
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
-
E.
licenseStatus
Indicates the current state or condition of a license in relation to its validity, permissions, or compliance.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.