Triple
T22028015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Session Description Protocol |
E544013
|
entity |
| Predicate | mediaDescriptionField |
P146327
|
FINISHED |
| Object | m= |
—
|
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: m= | Statement: [Session Description Protocol, mediaDescriptionField, m=]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaDescriptionField Context triple: [Session Description Protocol, mediaDescriptionField, m=]
-
A.
mediaDependentInterface
Indicates that one interface or interaction is contingent on, or varies according to, the characteristics or type of the media involved.
-
B.
mediaFeature
Indicates a characteristic, capability, or attribute of a media item that distinguishes how it is presented, functions, or is experienced.
-
C.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
D.
mediaAspect
Indicates the specific aspect ratio or dimensional proportion of a media item in relation to its width and height.
-
E.
mediaName
Indicates the name or title assigned to a media item (such as a work, file, or publication) in the relationship.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127cdf5c08190ac804664d6e56fe2 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:24 p.m.