Triple
T22814944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SDP capability negotiation extensions |
E565072
|
entity |
| Predicate | supportsCapabilityType |
P24486
|
FINISHED |
| Object | media format capabilities |
—
|
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: media format capabilities | Statement: [SDP capability negotiation extensions, supportsCapabilityType, media format capabilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCapabilityType Context triple: [SDP capability negotiation extensions, supportsCapabilityType, media format capabilities]
-
A.
hasCapType
Indicates that an entity possesses or is characterized by a specific type of cap or cap-like feature.
-
B.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
D.
usesCapabilityModel
Indicates that one entity employs or relies on a specific capability model to perform its functions or make decisions.
-
E.
hasTypeOfSupport
Indicates that one entity provides or is associated with a particular kind or category of support in relation to 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dcb872881909a031d8560635fce |
completed | April 29, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:33 p.m.