Triple
T37184657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-C2 |
E921290
|
entity |
| Predicate | supportsQAMOrder |
—
|
GENERATED |
| Object | 16-QAM |
—
|
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: supportsQAMOrder Context triple: [DVB-C2, supportsQAMOrder, 16-QAM]
-
A.
recognizesOrders
Indicates that one entity formally acknowledges and accepts the orders or directives issued by another entity.
-
B.
canOrder
Indicates that one entity has the ability or permission to place an order for another entity or item.
-
C.
supportsAskToBuy
Indicates that one entity enables or authorizes another entity to use an "Ask to Buy" approval process for purchases or requests.
-
D.
canCallToOrder
Indicates that one entity has the authority or ability to formally initiate or restore order in a meeting, session, or assembly involving another entity.
-
E.
supportsOrderAttribute
Indicates that one entity is capable of handling, recognizing, or providing a specified attribute associated with an order.
- F. None of above. chosen
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.