Triple
T31481073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktor Kramarenko |
E803141
|
entity |
| Predicate | designedStructureShape |
P195400
|
FINISHED |
| Object | rhombicuboctahedron |
—
|
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: rhombicuboctahedron | Statement: [Viktor Kramarenko, designedStructureShape, rhombicuboctahedron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedStructureShape Context triple: [Viktor Kramarenko, designedStructureShape, rhombicuboctahedron]
-
A.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
B.
designedStructureIn
Indicates that one entity is the designer or creator of a structure that is located within or associated with another specified entity or context.
-
C.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
D.
edificeShape
Indicates the geometric form or overall physical configuration that characterizes an edifice.
-
E.
shapeType
Indicates the specific geometric form or category that characterizes an entity’s shape.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
| PDg | Predicate description generation | batch_69fdd07724f88190a33ec602642d2ea3 |
completed | May 8, 2026, noon |
Created at: April 30, 2026, 9:32 p.m.