Triple
T31083779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GS1 Digital Link |
E792172
|
entity |
| Predicate | supportsDataCarrier |
—
|
GENERATED |
| Object | QR code |
—
|
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: supportsDataCarrier Context triple: [GS1 Digital Link, supportsDataCarrier, QR code]
-
A.
requiresCarrierSupport
Indicates that performing or enabling this action depends on support or approval from a carrier (e.g., a mobile network operator).
-
B.
supportsDataFrom
Indicates that one entity provides, validates, or underpins the data used or referenced by another entity.
-
C.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
-
D.
usesAsCarrier
chosen
Indicates that one entity employs another entity as a carrier or medium for transporting or conveying something.
-
E.
supportsMissionData
Indicates that one entity provides the necessary functionality or resources for another entity’s mission-related data to be stored, processed, or utilized.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:02 p.m.