Triple
T7858111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NetMeeting |
E182426
|
entity |
| Predicate | audioCodec |
P53672
|
FINISHED |
| Object | G.723.1 |
E444376
|
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: G.723.1 | Statement: [NetMeeting, audioCodec, G.723.1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: G.723.1 Context triple: [NetMeeting, audioCodec, G.723.1]
-
A.
G.723.1
chosen
G.723.1 is an ITU-T audio codec standard designed for low-bit-rate voice compression, commonly used in VoIP and multimedia communication systems.
-
B.
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.
-
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.729
G.729 is a widely used ITU-T audio codec standard that compresses voice for bandwidth-efficient transmission in VoIP and other telephony applications.
-
E.
G.711
G.711 is a widely used ITU-T audio codec standard for pulse code modulation (PCM) of voice in traditional telephony and VoIP systems.
- 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb1a76f8648190976b488d0d8658ef |
completed | March 31, 2026, 12:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbdf3828fc81908a118420a6b0a736 |
completed | March 31, 2026, 2:50 p.m. |
Created at: March 30, 2026, 4:52 p.m.