Triple
T22814043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCRtpSendParameters |
E565054
|
entity |
| Predicate | codecsElementType |
P149829
|
FINISHED |
| Object | RTCRtpCodecParameters |
—
|
LITERAL 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: RTCRtpCodecParameters | Statement: [RTCRtpSendParameters, codecsElementType, RTCRtpCodecParameters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codecsElementType Context triple: [RTCRtpSendParameters, codecsElementType, RTCRtpCodecParameters]
-
A.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
B.
commonlyAssociatedCodec
Indicates that one item is typically linked or paired with a particular codec in common usage or practice.
-
C.
codingSystemType
Indicates the classification or category of coding system used to encode or represent information in a given context.
-
D.
textEncoderType
Indicates the specific kind or configuration of encoder used to process or represent text in a system or model.
-
E.
codeUnitType
Indicates the specific kind or category of a code unit (such as a file, class, method, or module) that a given element belongs to.
- F. None of above. chosen
Provenance (4 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d62b0ec8190ac22909192e8a876 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:32 p.m.