Triple
T24816866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rhombicosidodecahedron |
E620946
|
entity |
| Predicate | isUniform |
P157744
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [rhombicosidodecahedron, isUniform, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUniform Context triple: [rhombicosidodecahedron, isUniform, true]
-
A.
areUniform
Indicates that all elements in a given set or collection share the same value, property, or characteristic.
-
B.
isUniformVariant
Indicates that one entity is a stylistic or formatting variant of another while preserving the same underlying content or structure.
-
C.
usesUniform
Indicates that one entity regularly wears or employs a standardized set of clothing or equipment designated as a uniform.
-
D.
requiresUniformity
Indicates that one entity imposes a condition that another entity (or set of entities) must be consistent or identical in a specified aspect.
-
E.
isNonUniform
Indicates that the property, distribution, or structure of something varies across its domain rather than remaining constant or uniform.
- 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_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 5:03 a.m.