Triple
T24816872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rhombicosidodecahedron |
E620946
|
entity |
| Predicate | hasNumberOfArchimedeanSolidIndex |
P160073
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [rhombicosidodecahedron, hasNumberOfArchimedeanSolidIndex, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfArchimedeanSolidIndex Context triple: [rhombicosidodecahedron, hasNumberOfArchimedeanSolidIndex, 11]
-
A.
hasNumberOfArches
Indicates the relationship specifying how many arches are present in or associated with a given entity.
-
B.
isUniformPolyhedron
Indicates that a polyhedron has regular polygons as faces and is vertex-transitive, so all its vertices are equivalent under the polyhedron’s symmetries.
-
C.
areNotKeplerPoinsotSolids
Indicates that the entities in question do not belong to the class of Kepler–Poinsot solids (the regular star polyhedra).
-
D.
hasFaceTransitivityCount
Indicates the number of times a face-related relation or transformation is applied or propagated through connected entities.
-
E.
isZonohedron
Indicates that the subject is a convex polyhedron whose faces are all centrally symmetric polygons, i.e., a zonohedron.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 18, 2026, 5:03 a.m.