Triple
T5480323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.248 |
E123451
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | H.323 |
E171421
|
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.323 | Statement: [H.248, relatedTo, H.323]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: H.323 Context triple: [H.248, relatedTo, H.323]
-
A.
H.323
chosen
H.323 is an ITU-T standard that defines protocols for voice, video, and data communication over packet-based networks such as IP.
-
B.
H.248
H.248 is an ITU-T protocol, also known as Megaco, used for controlling media gateways in next-generation and IP multimedia networks.
-
C.
SIP
SIP is the IATA airport code for Simferopol International Airport, the main air gateway to the Crimean Peninsula.
-
D.
G.722
G.722 is a wideband audio codec standard that provides higher-quality voice transmission than traditional narrowband codecs, commonly used in VoIP and teleconferencing applications.
-
E.
H.263
H.263 is a video compression standard developed primarily for low-bitrate communication such as video conferencing and early internet video applications.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf6c7a61848190970a4e34696791eb |
completed | March 22, 2026, 4:13 a.m. |
Created at: March 20, 2026, 2:09 p.m.