Triple
T11352278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.263 |
E268864
|
entity |
| Predicate | version |
P3286
|
FINISHED |
| Object | H.263v1 |
E268864
|
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.263v1 | Statement: [H.263, version, H.263v1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: H.263v1 Context triple: [H.263, version, H.263v1]
-
A.
H.263
chosen
H.263 is a video compression standard developed primarily for low-bitrate communication such as video conferencing and early internet video applications.
-
B.
H.261
H.261 is an early international video compression standard developed by the ITU-T for real-time video conferencing over ISDN and similar networks.
-
C.
MPEG-4 Part 2
MPEG-4 Part 2 is a video compression standard used for encoding digital video, notably in early MPEG-4 and DivX/Xvid formats.
-
D.
MPEG-4
MPEG-4 is a multimedia compression and coding standard widely used for digital audio, video, and interactive media distribution over the internet and other networks.
-
E.
H.239
H.239 is an ITU-T standard that enables dual video or data streams in video conferencing, allowing simultaneous transmission of live video and presentation content.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea24489081908fbf47fd2e6d709c |
completed | April 9, 2026, 6:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e58b8d5f5c8190a80a52f2063bb5b0 |
completed | April 20, 2026, 2:12 a.m. |
Created at: April 8, 2026, 9:33 p.m.