Triple
T26408644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keccak |
E663897
|
entity |
| Predicate | supportsArbitraryOutputLength |
P197474
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Keccak, supportsArbitraryOutputLength, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsArbitraryOutputLength Context triple: [Keccak, supportsArbitraryOutputLength, true]
-
A.
supportsArbitraryPrecisionArithmetic
Indicates that the subject system or component can perform arithmetic operations with numbers of virtually unlimited size and precision, beyond fixed hardware-imposed limits.
-
B.
supportsOutputType
Indicates that one entity is capable of producing, handling, or generating data or results of the specified output type.
-
C.
hasOutputSize
Indicates that an entity produces or is associated with an output characterized by a specific size or dimensional measure.
-
D.
supportsKeyLength
Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
-
E.
supportsVariableKeyLength
Indicates that an entity is capable of operating correctly with cryptographic keys of varying lengths rather than a single fixed key size.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
| PDg | Predicate description generation | batch_69fe96c0b760819093737292d33df165 |
completed | May 9, 2026, 2:06 a.m. |
Created at: April 26, 2026, 11:36 p.m.