Triple
T6034153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCRtpTransceiver |
E134376
|
entity |
| Predicate | createdWithMethod |
P25435
|
FINISHED |
| Object | RTCPeerConnection.addTransceiver() |
—
|
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.addTransceiver() | Statement: [RTCRtpTransceiver, createdWithMethod, RTCPeerConnection.addTransceiver()]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdWithMethod Context triple: [RTCRtpTransceiver, createdWithMethod, RTCPeerConnection.addTransceiver()]
-
A.
createdByMethod
chosen
Indicates that something was produced, generated, or brought into existence through a specific method or procedure.
-
B.
firstCreatedUsing
Indicates that one entity was initially produced or brought into existence through the use, application, or involvement of another entity.
-
C.
createdAs
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified by another entity.
-
D.
createdByConstructionOf
Indicates that something comes into existence as a result of a construction process or building activity performed by an agent.
-
E.
createdIn
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b220608190b156be95632cf3b3 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.