Triple
T22814059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCRtpSendParameters |
E565054
|
entity |
| Predicate | modifiableVia |
P12017
|
FINISHED |
| Object | RTCRtpSender.setParameters |
—
|
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: RTCRtpSender.setParameters | Statement: [RTCRtpSendParameters, modifiableVia, RTCRtpSender.setParameters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modifiableVia Context triple: [RTCRtpSendParameters, modifiableVia, RTCRtpSender.setParameters]
-
A.
mayBeModifiedBy
chosen
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
B.
isMutable
Indicates that an entity can be changed or modified after it has been created or initially defined.
-
C.
modification
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
-
D.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter another entity.
-
E.
mayDefine
Indicates that one entity has the authority or capability to specify, establish, or determine the form, content, or rules of another entity.
- F. None of above.
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_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. |
Created at: April 17, 2026, 3:32 p.m.