Triple
T37163507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JVT |
E920736
|
entity |
| Predicate | standardDesignationITU |
P30509
|
FINISHED |
| Object | ITU-T H.264 |
—
|
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: ITU-T H.264 | Statement: [JVT, standardDesignationITU, ITU-T H.264]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardDesignationITU Context triple: [JVT, standardDesignationITU, ITU-T H.264]
-
A.
internationalDesignation
chosen
Indicates that an entity has been assigned a formal status, code, or recognition by an international body or under an internationally agreed system.
-
B.
ICAOTypeDesignator
Indicates the standardized aircraft type code assigned by ICAO that specifies the model or family of an aircraft used in aviation operations and documentation.
-
C.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
-
D.
systemDesignation
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
-
E.
callsignOrDesignation
Indicates that one entity serves as the callsign or formal designation used to identify another entity in communication or operational contexts.
- 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_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 3, 2026, 4:15 p.m.