Triple
T9326002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Trade Item Number |
E224385
|
entity |
| Predicate | hasCheckDigitCalculation |
P11854
|
FINISHED |
| Object | 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: modulo-10 algorithm | Statement: [Global Trade Item Number, hasCheckDigitCalculation, modulo-10 algorithm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckDigitCalculation Context triple: [Global Trade Item Number, hasCheckDigitCalculation, 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.
hasDigitCount
Indicates that one entity has a total number of digits equal to the value specified by the other entity.
-
D.
checksum
Indicates that a value has been computed from data to verify its integrity or detect errors in transmission or storage.
-
E.
hasDigitSet
Indicates that an entity is associated with a specific set or collection of digits.
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f88e988190bb896a3d7c3c723c |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.