Triple
T33084180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMC+ |
E846591
|
entity |
| Predicate | hasLinearChannelBundles |
P195826
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [AMC+, hasLinearChannelBundles, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLinearChannelBundles Context triple: [AMC+, hasLinearChannelBundles, yes]
-
A.
hasFullBandwidthChannels
Indicates that the subject possesses communication channels that operate at the maximum or designated full data transmission capacity.
-
B.
isAssociatedWithLineBundle
Indicates that there exists a relationship linking an entity to a specific line bundle, typically signifying that the entity is defined, structured, or characterized in terms of that line bundle.
-
C.
hasFrequencyChannels
Indicates that an entity is associated with, or operates over, one or more specific frequency channels.
-
D.
hasOpticalChannels
Indicates that an entity possesses one or more optical communication or signal-transmission channels.
-
E.
hasCanalOrChannel
Indicates that one entity possesses, contains, or is traversed by a canal or channel that serves as a conduit or passageway.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
| PDg | Predicate description generation | batch_69fde9fb68388190ada4a7018e2a2f76 |
completed | May 8, 2026, 1:49 p.m. |
Created at: May 1, 2026, 1:26 a.m.