Triple
T37164294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-MHP |
E920752
|
entity |
| Predicate | supportsApplicationModel |
P80956
|
FINISHED |
| Object | broadcast-centric applications |
—
|
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: broadcast-centric applications | Statement: [DVB-MHP, supportsApplicationModel, broadcast-centric applications]
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 (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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.