Triple
T26408656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keccak |
E663897
|
entity |
| Predicate | hasDesignProperty |
P177101
|
FINISHED |
| Object | bit-oriented design |
—
|
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: bit-oriented design | Statement: [Keccak, hasDesignProperty, bit-oriented design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignProperty Context triple: [Keccak, hasDesignProperty, bit-oriented design]
-
A.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
C.
hasDesignContext
Indicates that something is associated with, or defined within, a particular design context or design environment.
-
D.
hasDesignRelationship
Indicates that there exists a design-based relationship or association between two entities, such as one influencing, constraining, or deriving from the design of the other.
-
E.
hasDesignIntent
Indicates that one entity embodies or reflects the planned purpose, function, or conceptual intent defined by another entity.
- 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_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 26, 2026, 11:36 p.m.