Triple

T24806901
Position Surface form Disambiguated ID Type / Status
Subject rhombicuboctahedron E620678 entity
Predicate hasRelatedPolyhedron P33476 FINISHED
Object great rhombicuboctahedron NE NERFINISHED

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: great rhombicuboctahedron | Statement: [rhombicuboctahedron, hasRelatedPolyhedron, great rhombicuboctahedron]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRelatedPolyhedron
Context triple: [rhombicuboctahedron, hasRelatedPolyhedron, great rhombicuboctahedron]
  • A. hasRelatedPolygon
    Indicates that one entity is associated with another entity that is represented or defined as a polygon.
  • B. hasDualPolyhedron
    Indicates that one polyhedron is the dual of another, meaning their vertices and faces correspond in an inverse, structure-preserving way.
  • C. hasShapeRelation
    Indicates that one entity is related to another through a specific geometric or spatial shape relationship (such as similarity, congruence, or containment of shape).
  • D. 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.
  • E. hasRelation chosen
    Indicates that there exists some specified relationship or association between two entities.
  • 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_69f6562fd3488190be1acd8c526a28d2 completed May 2, 2026, 7:53 p.m.
PD Predicate disambiguation batch_69f651a731508190bb0c8c2462eba224 completed May 2, 2026, 7:33 p.m.
Created at: April 18, 2026, 4:50 a.m.