Triple
T24816877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rhombicosidodecahedron |
E620946
|
entity |
| Predicate | hasDihedralAngleBetweenTrianglesAndPentagons |
P160884
|
FINISHED |
| Object | 150 degrees |
—
|
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: 150 degrees | Statement: [rhombicosidodecahedron, hasDihedralAngleBetweenTrianglesAndPentagons, 150 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDihedralAngleBetweenTrianglesAndPentagons Context triple: [rhombicosidodecahedron, hasDihedralAngleBetweenTrianglesAndPentagons, 150 degrees]
-
A.
hasNumberOfPentagonalFaces
Indicates the relationship between an object and the count of its pentagonal faces.
-
B.
hasDihedralAngle
chosen
Indicates that there is a specific angle formed between two intersecting planes or faces.
-
C.
hasPentagons
Indicates that an entity possesses or contains one or more pentagon-shaped components or regions.
-
D.
hasTriangleAngle
Indicates that a triangle possesses a specific angle as one of its interior angles.
-
E.
hasTriangle
Indicates that an entity possesses, contains, or is associated with a triangle.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 5:03 a.m.