Triple
T37184705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-C2 |
E921290
|
entity |
| Predicate | supportsGuardInterval |
—
|
GENERATED |
| Object | 1/128 |
—
|
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: supportsGuardInterval Context triple: [DVB-C2, supportsGuardInterval, 1/128]
-
A.
supportsGuardIntervals
chosen
Indicates that one entity provides or is compatible with guard intervals used by another entity in a timing- or transmission-related context.
-
B.
hasGuardUnit
Indicates that an entity is protected or overseen by a specific guard unit.
-
C.
hasGatekeeper
Indicates that one entity serves as a controlling or mediating gatekeeper for access to another entity.
-
D.
hasInterval
Indicates that something is associated with a specific span or range between two points in time, space, or value.
-
E.
hasIntervalStructure
Indicates that something possesses or is organized according to a specific interval-based structure or pattern.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.