Triple
T26253295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chebyshev distance |
E656653
|
entity |
| Predicate | unitBallShape |
P160414
|
FINISHED |
| Object | hypercube |
—
|
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: hypercube | Statement: [Chebyshev distance, unitBallShape, hypercube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitBallShape Context triple: [Chebyshev distance, unitBallShape, hypercube]
-
A.
unitBall
Indicates that one entity is the unit ball (all points within distance 1 of the origin, typically in a given norm) associated with or defined in relation to the other entity.
-
B.
unitBallProperty
Indicates that the object satisfies the defining characteristics or constraints of a unit ball (typically radius 1 centered at a reference point) within a given space.
-
C.
usesBallShape
Indicates that one entity employs or incorporates a ball-like (spherical) shape in its form, design, or operation.
-
D.
სფერო
Indicates a general field, domain, or area within which something operates, applies, or is categorized.
-
E.
sphereDiameter
Indicates the measurement of the distance across a sphere passing through its center, relating the sphere to its diameter.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dcc29cc81908880bd825cb12141 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 9:07 p.m.