Triple
T37164294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-MHP |
E920752
|
entity |
| Predicate | supportsApplicationModel |
—
|
GENERATED |
| Object | broadcast-centric applications |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsApplicationModel Context triple: [DVB-MHP, supportsApplicationModel, broadcast-centric applications]
-
A.
applicationModelSupport
chosen
Indicates that one entity provides support, compatibility, or services for another entity’s application model or application-level behavior.
-
B.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
-
C.
supportedModel
Indicates that one entity provides compatibility with, or operational backing for, a particular model.
-
D.
supportsAccessModel
Indicates that one entity enables, permits, or is compatible with a particular access model used by another entity.
-
E.
supportsExtensionModel
Indicates that one entity provides compatibility or functionality for using a specified extension model associated with another entity.
- F. None of above.
Provenance (1 batch)
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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.