Triple
T12516402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POSIX ustar format |
E299200
|
entity |
| Predicate | checksumAlgorithm |
P35572
|
FINISHED |
| Object | simple unsigned byte sum over header |
—
|
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: simple unsigned byte sum over header | Statement: [POSIX ustar format, checksumAlgorithm, simple unsigned byte sum over header]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checksumAlgorithm Context triple: [POSIX ustar format, checksumAlgorithm, simple unsigned byte sum over header]
-
A.
checksum
chosen
Indicates that a value has been computed from data to verify its integrity or detect errors in transmission or storage.
-
B.
checkDigitAlgorithm
Indicates the algorithm or method used to compute or validate a check digit for an identifier or code.
-
C.
algorithmType
Indicates the specific kind or category of algorithm associated with an entity or process.
-
D.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
E.
digestSize
Indicates the size or length of a computed digest (such as a hash or checksum) produced from some data.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.