Triple
T20614981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luhn algorithm variant |
E506542
|
entity |
| Predicate | checkDigitCondition |
P11854
|
FINISHED |
| Object | total sum modulo 10 equals 0 for valid ISIN |
—
|
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: total sum modulo 10 equals 0 for valid ISIN | Statement: [Luhn algorithm variant, checkDigitCondition, total sum modulo 10 equals 0 for valid ISIN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checkDigitCondition Context triple: [Luhn algorithm variant, checkDigitCondition, total sum modulo 10 equals 0 for valid ISIN]
-
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.
isDigitSequence
Indicates that a given value consists solely of one or more numeric digit characters arranged in sequence.
-
E.
digitType
Indicates the specific category or kind of digit (such as numerical, symbolic, or positional type) associated with an entity.
- 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aadaf47881909e93efb535c6c1e3 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.