Triple
T37163501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JVT |
E920736
|
entity |
| Predicate | primaryStandardDeveloped |
P30412
|
FINISHED |
| Object | H.264 |
E53638
|
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: H.264 | Statement: [JVT, primaryStandardDeveloped, H.264]
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 (4 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a402bba279c81908800321a32b6f2c5 |
completed | June 27, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.