Triple
T2007422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EAN-13 barcode system |
E43616
|
entity |
| Predicate | checkDigitComputationMethod |
P11854
|
FINISHED |
| Object | modulo 10 |
—
|
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 | Statement: [EAN-13 barcode system, checkDigitComputationMethod, modulo 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checkDigitComputationMethod Context triple: [EAN-13 barcode system, checkDigitComputationMethod, modulo 10]
-
A.
checkDigitAlgorithm
chosen
Indicates the algorithm or method used to compute or validate a check digit for an identifier or code.
-
B.
hasCheckDigit
Indicates that an identifier or code includes a calculated check digit used to verify its correctness or integrity.
-
C.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
D.
hasDigitCount
Indicates that one entity has a total number of digits equal to the value specified by the other entity.
-
E.
FIBACode
Indicates a relationship where an entity is assigned or associated with a specific FIBA (International Basketball Federation) identification code.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8999e108190a07daa01452a5dab |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.