Triple
T37163508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JVT |
E920736
|
entity |
| Predicate | standardDesignationISOIEC |
P18878
|
FINISHED |
| Object | ISO/IEC 14496-10 |
—
|
NE NERFINISHED |
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: ISO/IEC 14496-10 | Statement: [JVT, standardDesignationISOIEC, ISO/IEC 14496-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardDesignationISOIEC Context triple: [JVT, standardDesignationISOIEC, ISO/IEC 14496-10]
-
A.
isInternationalStandard
Indicates that something has been formally recognized or adopted as a standard at the international level.
-
B.
isPartOfStandardizationSystem
Indicates that something belongs to, or is included within, a defined standardization framework, scheme, or system.
-
C.
internationalDesignation
Indicates that an entity has been assigned a formal status, code, or recognition by an international body or under an internationally agreed system.
-
D.
introducedAsInternationalStandard
Indicates that something has been formally adopted and announced as an international standard.
-
E.
standardNumberStandardizedBy
chosen
Indicates that a standard number has been formally defined, approved, or regulated by a specific standardizing authority or organization.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: May 3, 2026, 4:15 p.m.