Triple
T1166437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCRtpReceiver |
E24809
|
entity |
| Predicate | returnsFromMethod |
P16989
|
FINISHED |
| Object | RTCPeerConnection.addTrack |
—
|
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.addTrack | Statement: [RTCRtpReceiver, returnsFromMethod, RTCPeerConnection.addTrack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnsFromMethod Context triple: [RTCRtpReceiver, returnsFromMethod, RTCPeerConnection.addTrack]
-
A.
returnedFrom
chosen
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
B.
returnedWith
Indicates that an entity came back or was brought back accompanied by, or in possession of, another specified entity.
-
C.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
D.
returnService
Indicates a relationship where a service that was previously provided is being sent back, reversed, or requested to be undone or refunded.
-
E.
returnBasis
Indicates the basis, method, or terms under which something is returned (e.g., goods, funds, or data) from one party or context to another.
- 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_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. |
Created at: March 1, 2026, 7:45 p.m.