Triple
T21224632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3551 |
E523057
|
entity |
| Predicate | definesPayloadType |
P56536
|
FINISHED |
| Object | H263 |
—
|
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: H263 | Statement: [RFC 3551, definesPayloadType, H263]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: H263 Context triple: [RFC 3551, definesPayloadType, H263]
-
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.
H.267
H.267 is a member of the H.26x family of international video compression standards designed for efficient digital video coding.
-
D.
H.262
H.262 is an international video compression standard, better known as MPEG-2 Part 2, widely used for digital television broadcasting and DVD video.
-
E.
H.324
H.324 is an ITU-T multimedia communication protocol designed for real-time audio, video, and data transmission over circuit-switched telephone networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734aa82c4819086cef6364619b4e9 |
completed | April 21, 2026, 8:26 a.m. |
Created at: April 16, 2026, 3:44 p.m.