Triple
T5015945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HDMI |
E112740
|
entity |
| Predicate | firstSpecificationVersion |
P11996
|
FINISHED |
| Object | 1.0 |
—
|
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: 1.0 | Statement: [HDMI, firstSpecificationVersion, 1.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSpecificationVersion Context triple: [HDMI, firstSpecificationVersion, 1.0]
-
A.
firstSpecified
Indicates that the subject is the earliest or initial entity explicitly designated or chosen among a set of specified entities.
-
B.
firstReleaseVersion
chosen
Indicates the specific version identifier associated with the initial public release of something.
-
C.
primarySpecification
Indicates that one specification is the main or authoritative specification associated with an entity, distinguishing it from any secondary or supplementary specifications.
-
D.
firstFullVersionReference
Indicates that one entity serves as the initial complete or fully realized version to which another entity refers or is linked.
-
E.
principalVersionFor
Indicates a relationship where one version of an entity is designated as the primary or authoritative version for another related entity.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732f4c5c8190b90f8e4daab458ee |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.