Triple
T19451773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silicon Image |
E486628
|
entity |
| Predicate | roleInStandard |
P28582
|
FINISHED |
| Object | HDMI founding member |
—
|
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: HDMI founding member | Statement: [Silicon Image, roleInStandard, HDMI founding member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInStandard Context triple: [Silicon Image, roleInStandard, HDMI founding member]
-
A.
roleInStandards
chosen
Indicates that an entity holds a specific role or function in the creation, maintenance, or governance of standards.
-
B.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
C.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
D.
roleInSpecification
Indicates that an entity participates in a specification with a particular role or function within that specification.
-
E.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63392aab08190aab09b7c356e5b10 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.