Triple
T24806910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rhombicuboctahedron |
E620678
|
entity |
| Predicate | hasCircumscribableProperty |
P23698
|
FINISHED |
| Object | can be inscribed in a sphere |
—
|
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: can be inscribed in a sphere | Statement: [rhombicuboctahedron, hasCircumscribableProperty, can be inscribed in a sphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCircumscribableProperty Context triple: [rhombicuboctahedron, hasCircumscribableProperty, can be inscribed in a sphere]
-
A.
haveProperty
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
B.
hasSubproperty
Indicates that one property is a more specific version of another property, inheriting its meaning and constraints.
-
C.
circumscribedBy
Indicates that one entity is completely enclosed or bounded on all sides by another entity.
-
D.
isContributingPropertyTo
Indicates that one property plays a role in producing, influencing, or determining another property or overall outcome.
-
E.
hasSemanticRestriction
Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
- 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_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:50 a.m.