Triple
T24806880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rhombicuboctahedron |
E620678
|
entity |
| Predicate | hasVertexConfiguration |
P13644
|
FINISHED |
| Object | 3.4.4.4 |
—
|
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: 3.4.4.4 | Statement: [rhombicuboctahedron, hasVertexConfiguration, 3.4.4.4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVertexConfiguration Context triple: [rhombicuboctahedron, hasVertexConfiguration, 3.4.4.4]
-
A.
hasVertex
Indicates that an object, typically a geometric shape or graph, includes a specified vertex as one of its corner or node points.
-
B.
hasConfiguration
chosen
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
C.
hasVertexSet
Indicates that a graph or geometric object is associated with, or defined by, a specific set of vertices.
-
D.
hasConfigurationFormat
Indicates that an entity uses or is associated with a specific configuration format for its settings or parameters.
-
E.
hasAxisConfiguration
Indicates that one entity specifies or defines the axis arrangement, orientation, or setup used by 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:50 a.m.