Triple
T28508648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unix crypt(3) |
E721424
|
entity |
| Predicate | originalKeySpace |
P77467
|
FINISHED |
| Object | 56-bit DES key |
—
|
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: 56-bit DES key | Statement: [Unix crypt(3), originalKeySpace, 56-bit DES key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalKeySpace Context triple: [Unix crypt(3), originalKeySpace, 56-bit DES key]
-
A.
keySpace
Indicates the logical namespace or partition within a data store or system in which a particular key or set of keys is defined and managed.
-
B.
keySpaceSize
chosen
Indicates the total number of distinct keys that can exist within a given key space or key domain.
-
C.
hasKeySpace
Indicates that one entity defines, owns, or is associated with the namespace or set of valid keys used to identify or access elements in another entity.
-
D.
databaseKey
Indicates that one entity serves as a unique key or identifier for accessing or referencing another entity within a database.
-
E.
associatedKey
Indicates that one entity serves as a key or identifier that is logically or functionally linked to another 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: April 28, 2026, 3:11 a.m.