Triple
T12025184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rsync algorithm |
E286256
|
entity |
| Predicate | checksumType |
P35572
|
FINISHED |
| Object | rolling weak checksum |
—
|
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: rolling weak checksum | Statement: [rsync algorithm, checksumType, rolling weak checksum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checksumType Context triple: [rsync algorithm, checksumType, rolling weak checksum]
-
A.
checksum
chosen
Indicates that a value has been computed from data to verify its integrity or detect errors in transmission or storage.
-
B.
hasCheckDigit
Indicates that an identifier or code includes a calculated check digit used to verify its correctness or integrity.
-
C.
supportsJournalChecksumming
Indicates that an entity provides functionality to compute and verify checksums for journal data to ensure its integrity.
-
D.
checkDigitAlgorithm
Indicates the algorithm or method used to compute or validate a check digit for an identifier or code.
-
E.
signatureType
Indicates the specific kind or category of a signature associated with an entity or action.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.