Triple
T37163554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VCEG |
E920737
|
entity |
| Predicate | standardNumberSeries |
P20334
|
FINISHED |
| Object | H.26x |
—
|
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: H.26x | Statement: [VCEG, standardNumberSeries, H.26x]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardNumberSeries Context triple: [VCEG, standardNumberSeries, H.26x]
-
A.
standardNumber
Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
-
B.
standardNumberingScheme
chosen
Indicates that there is a specific, commonly accepted numbering system or convention being applied to identify or order the related entities.
-
C.
namingSeries
Indicates that one entity serves as the naming convention or series under which another entity is titled or labeled.
-
D.
standardNumberFamily
Indicates that an entity belongs to a defined family or group of related standard numbers (e.g., variants, editions, or closely associated identifiers).
-
E.
numberOfSeries
Indicates the total count of distinct series associated with or contained within a given 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:15 p.m.