Triple
T8651476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAS Registry Number |
E205108
|
entity |
| Predicate | usesCheckDigitAlgorithm |
P11854
|
FINISHED |
| Object | modulo 10 weighted sum |
—
|
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 weighted sum | Statement: [CAS Registry Number, usesCheckDigitAlgorithm, modulo 10 weighted sum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCheckDigitAlgorithm Context triple: [CAS Registry Number, usesCheckDigitAlgorithm, modulo 10 weighted sum]
-
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.
usesIntegrityCheck
Indicates that an entity employs a mechanism to verify the integrity or correctness of data, code, or operations.
-
E.
checksum
Indicates that a value has been computed from data to verify its integrity or detect errors in transmission or storage.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48150e6c8190a7a3b92b4b640858 |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.