Triple
T31083628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Location Number |
E792169
|
entity |
| Predicate | hasCheckDigitAlgorithm |
P11854
|
FINISHED |
| Object | GS1 modulo-10 algorithm |
—
|
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: GS1 modulo-10 algorithm | Statement: [Global Location Number, hasCheckDigitAlgorithm, GS1 modulo-10 algorithm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckDigitAlgorithm Context triple: [Global Location Number, hasCheckDigitAlgorithm, GS1 modulo-10 algorithm]
-
A.
hasCheckDigit
Indicates that an identifier or code includes a calculated check digit used to verify its correctness or integrity.
-
B.
checkDigitAlgorithm
chosen
Indicates the algorithm or method used to compute or validate a check digit for an identifier or code.
-
C.
hasRoutingCodeDigit
Indicates that an entity’s routing code contains a specific digit at a particular position or as part of its structure.
-
D.
hasDigitCount
Indicates that one entity has a total number of digits equal to the value specified by the other entity.
-
E.
hasAlgorithmName
Indicates that an entity is associated with or identified by a specific algorithm name.
- F. None of above.
Provenance (3 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 29, 2026, 9:02 p.m.