Triple
T26253313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chebyshev distance |
E656653
|
entity |
| Predicate | greaterOrEqualThan |
P160415
|
FINISHED |
| Object | Euclidean distance on R^n |
—
|
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: Euclidean distance on R^n | Statement: [Chebyshev distance, greaterOrEqualThan, Euclidean distance on R^n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: greaterOrEqualThan Context triple: [Chebyshev distance, greaterOrEqualThan, Euclidean distance on R^n]
-
A.
largerThan
Indicates that one entity has a greater size, extent, or magnitude than another entity.
-
B.
lessThanOrEqualTo
Indicates that one entity’s value is smaller than or exactly equal to another entity’s value.
-
C.
isHigherThan
Indicates that one entity has a greater value, level, or position than another entity.
-
D.
higherNormThan
Indicates that one entity has a greater norm (such as magnitude, size, or standard measure) than another entity.
-
E.
meetsAtLeast
Indicates that one entity encounters or comes into contact with another entity at least a specified minimum number of times or to a minimum required degree.
- 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.