Triple
T28508649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unix crypt(3) |
E721424
|
entity |
| Predicate | originalPasswordLengthLimit |
P198308
|
FINISHED |
| Object | 8 characters |
—
|
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: 8 characters | Statement: [Unix crypt(3), originalPasswordLengthLimit, 8 characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPasswordLengthLimit Context triple: [Unix crypt(3), originalPasswordLengthLimit, 8 characters]
-
A.
passwordStorageRequirement
Indicates that there is a specified condition or standard governing how passwords must be stored.
-
B.
maximumAuthorizedStrength
Indicates the highest allowable level or quantity of a resource, capacity, or personnel that is officially permitted.
-
C.
initialAuthorizedStrength
Indicates the originally approved or designated level, size, or capacity of a force, group, or resource at the time it was first authorized.
-
D.
recommendedKeyLength
Indicates the suggested or optimal length that a cryptographic key should have for secure use in a given context.
-
E.
hasMinimumLength
Indicates that the length of an entity (such as a sequence, string, or collection) is greater than or equal to a specified minimum value.
- F. None of above. chosen
Provenance (4 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_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
| PDg | Predicate description generation | batch_69fedd5915588190bd884054e4be0414 |
completed | May 9, 2026, 7:08 a.m. |
Created at: April 28, 2026, 3:11 a.m.