Triple
T17598609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pipfile.lock |
E428635
|
entity |
| Predicate | hashesAre |
P35572
|
FINISHED |
| Object | cryptographic hashes of distributions |
—
|
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: cryptographic hashes of distributions | Statement: [Pipfile.lock, hashesAre, cryptographic hashes of distributions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hashesAre Context triple: [Pipfile.lock, hashesAre, cryptographic hashes of distributions]
-
A.
requiresHashableElements
Indicates that the relationship or operation can only be applied when all involved elements support hashing (i.e., can be used as keys in hash-based structures).
-
B.
checksum
chosen
Indicates that a value has been computed from data to verify its integrity or detect errors in transmission or storage.
-
C.
hasCrypt
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
-
D.
hasEquivalent
Indicates that two entities are considered equal in value, meaning, or function within a given context.
-
E.
hasEntropy
Indicates that an entity possesses or is characterized by a certain amount or state of entropy, typically reflecting its degree of disorder or uncertainty.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c474e5481909d2736241b592dab |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.