Triple
T24816886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rhombicosidodecahedron |
E620946
|
entity |
| Predicate | hasEdgeLengthSymbol |
P73890
|
FINISHED |
| Object | a |
—
|
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: a | Statement: [rhombicosidodecahedron, hasEdgeLengthSymbol, a]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEdgeLengthSymbol Context triple: [rhombicosidodecahedron, hasEdgeLengthSymbol, a]
-
A.
hasEdgeCount
Indicates that there is a specified number of edges associated with an entity, such as a graph or geometric shape.
-
B.
hasEdgeGraph
Indicates that there is an edge (a direct connection or link) present within a graph between specified nodes or components.
-
C.
hasBorderLengthCharacteristic
Indicates that a border is associated with a specific length-related property or characteristic.
-
D.
haveEqualEdgeLengths
Indicates that the connected entities possess edges whose lengths are all equal to one another.
-
E.
hasSIBaseDimensionSymbol
chosen
Indicates that a physical quantity or unit is associated with a specific SI base dimension symbol (e.g., L, M, T) representing its fundamental dimensional nature.
- 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_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:03 a.m.