Triple
T18293997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCITT |
E438183
|
entity |
| Predicate | notableStandard |
P321
|
FINISHED |
| Object | G.729 |
—
|
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: G.729 | Statement: [CCITT, notableStandard, G.729]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: G.729 Context triple: [CCITT, notableStandard, G.729]
-
A.
G.729
chosen
G.729 is a widely used ITU-T audio codec standard that compresses voice for bandwidth-efficient transmission in VoIP and other telephony applications.
-
B.
G.728
G.728 is an ITU-T speech codec that provides low-delay, 16 kbit/s compression for high-quality voice communication, commonly used in telephony and VoIP applications.
-
C.
G.726
G.726 is an ITU-T audio codec standard that specifies adaptive differential pulse-code modulation (ADPCM) for compressing voice signals at multiple bit rates, commonly used in telephony.
-
D.
G.727
G.727 is an ITU-T audio compression standard that provides adaptive differential pulse-code modulation (ADPCM) for efficient voice transmission at multiple bit rates.
-
E.
G.721
G.721 is an ITU-T (formerly CCITT) audio coding standard that defines 32 kbit/s ADPCM compression for digital telephony.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5010205bc8190a32fe731ead3d988 |
completed | April 19, 2026, 4:21 p.m. |
Created at: April 10, 2026, 10:35 a.m.