Triple
T28620124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPEG-DASH |
E724357
|
entity |
| Predicate | segmentSelectionControlledBy |
P70862
|
FINISHED |
| Object | client |
—
|
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: client | Statement: [MPEG-DASH, segmentSelectionControlledBy, client]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: segmentSelectionControlledBy Context triple: [MPEG-DASH, segmentSelectionControlledBy, client]
-
A.
rangeControlledBy
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
B.
controlSegment
chosen
Indicates that one entity governs, directs, or regulates a specific segment or portion of another entity or system.
-
C.
entrySelectionMethod
Indicates the method or criteria used to select or admit an entity into a particular group, system, or context.
-
D.
selectionDescribedIn
Indicates that a particular selection or choice is documented, explained, or detailed within a specified description or source.
-
E.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:33 a.m.