Triple
T5015682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SBC |
E112735
|
entity |
| Predicate | supportsSubbands |
P61515
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [SBC, supportsSubbands, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSubbands Context triple: [SBC, supportsSubbands, 4]
-
A.
supportsSingleFrequencyNetworks
Indicates that an entity enables or is compatible with operating in single frequency networks, where multiple transmitters use the same frequency to provide coordinated coverage.
-
B.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
C.
supportsChannels
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
-
D.
hasBandRange
Indicates that one entity has an associated range or span of bands (such as frequency or wavelength intervals) defined by the other entity.
-
E.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
- F. None of above. chosen
Provenance (4 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732f4c5c8190b90f8e4daab458ee |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:35 p.m.