Triple
T1166424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCRtpReceiver |
E24809
|
entity |
| Predicate | exposes |
P25434
|
FINISHED |
| Object | incoming media track |
—
|
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: incoming media track | Statement: [RTCRtpReceiver, exposes, incoming media track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposes Context triple: [RTCRtpReceiver, exposes, incoming media track]
-
A.
exposed
Indicates that one entity has been made visible, revealed, or left unprotected to another entity or to some external influence.
-
B.
discloses
Indicates that one entity reveals, makes known, or provides previously non-public information to another entity or to the public.
-
C.
expresses
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
-
D.
exposureType
Indicates the specific manner or context in which one entity is exposed to another entity, condition, or influence.
-
E.
notableExposure
Indicates that an entity has received significant public attention, visibility, or coverage, making it notably exposed or recognized.
- 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.