Triple
T30483806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMPTE ST 2094-2 |
E775658
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object |
Philips HDR dynamic metadata
Philips HDR dynamic metadata is a high dynamic range video technology that uses scene-by-scene or frame-by-frame metadata to optimize image quality on compatible displays.
|
E1916361
|
NE 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: Philips HDR dynamic metadata | Statement: [SMPTE ST 2094-2, alsoKnownAs, Philips HDR dynamic metadata]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Philips HDR dynamic metadata Triple: [SMPTE ST 2094-2, alsoKnownAs, Philips HDR dynamic metadata]
Generated description
Philips HDR dynamic metadata is a high dynamic range video technology that uses scene-by-scene or frame-by-frame metadata to optimize image quality on compatible displays.
Provenance (5 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6874496048190bcc4b78a31d5d455 |
completed | May 2, 2026, 11:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27ac2821988190b00de2a44a5e0083 |
completed | June 9, 2026, 6:01 a.m. |
| NEDg | Description generation | batch_6a27acc30d088190b6feb313b8979b1d |
completed | June 9, 2026, 6:03 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a27ad92d8388190a23f21530d90173c |
completed | June 9, 2026, 6:07 a.m. |
Created at: April 29, 2026, 8:13 p.m.