Triple
T26253292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chebyshev distance |
E656653
|
entity |
| Predicate | metricSpaceType |
P31180
|
FINISHED |
| Object | norm-induced metric |
—
|
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: norm-induced metric | Statement: [Chebyshev distance, metricSpaceType, norm-induced metric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricSpaceType Context triple: [Chebyshev distance, metricSpaceType, norm-induced metric]
-
A.
metricSpaceProperty
Indicates that a specified property or condition holds for a metric space, characterizing how its distance structure behaves.
-
B.
metricType
chosen
Indicates the specific category or kind of measurement that a given metric represents.
-
C.
spatialSubmetric
Indicates that one spatial metric or measurement is a restricted or subordinate part of another, broader spatial metric.
-
D.
distanceMetric
Indicates a quantitative measure of how far apart two entities are within a given space or according to a specified metric.
-
E.
dimensionType
Indicates the specific kind or category of dimension that characterizes how something is measured or structured.
- 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_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. |
Created at: April 26, 2026, 9:07 p.m.