Triple
T1166427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCRtpReceiver |
E24809
|
entity |
| Predicate | createdByMethod |
P25435
|
FINISHED |
| Object | RTCPeerConnection.getReceivers |
—
|
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: RTCPeerConnection.getReceivers | Statement: [RTCRtpReceiver, createdByMethod, RTCPeerConnection.getReceivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdByMethod Context triple: [RTCRtpReceiver, createdByMethod, RTCPeerConnection.getReceivers]
-
A.
createdBy
Indicates that something was brought into existence, produced, or authored through the actions or efforts of a specific agent or entity.
-
B.
createdByAct
Indicates that something came into existence or was produced as the result of a specific act or action.
-
C.
cardinalCreatedBy
Indicates that a cardinal (a high-ranking clergy member) was created or appointed by a specific authority or person.
-
D.
appointedByMethod
Indicates that an appointment or designation of a role or position was made using a specified method or procedure.
-
E.
calledBy
Indicates that one entity initiates a call or invocation to another entity.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccc62a88190882d8801908015a4 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc8ae87c81908ca5d94f63ad0e80 |
completed | March 1, 2026, 10:24 p.m. |
Created at: March 1, 2026, 7:45 p.m.