Triple
T37163501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JVT |
E920736
|
entity |
| Predicate | primaryStandardDeveloped |
—
|
GENERATED |
| Object | H.264 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStandardDeveloped Context triple: [JVT, primaryStandardDeveloped, H.264]
-
A.
developsStandardsFor
chosen
Indicates that one entity creates, defines, or establishes formal standards, guidelines, or specifications for another entity or domain.
-
B.
firstStandardApproved
Indicates that an entity is the earliest or initial standard that has received formal approval.
-
C.
firstStandardized
Indicates that an entity is the earliest or primary instance to which a standard or uniform specification has been first applied among comparable entities.
-
D.
introducedStandard
Indicates that an entity formally brought a standard into existence or put it into official use.
-
E.
firstStandard
Indicates that the subject is the earliest or primary instance in a defined standard, sequence, or set of reference criteria.
- F. None of above.
Provenance (1 batch)
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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.