Triple
T24286126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KNN |
E605673
|
entity |
| Predicate | commonDistanceMetric |
P27195
|
FINISHED |
| Object | Euclidean distance |
—
|
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 | Statement: [KNN, commonDistanceMetric, Euclidean distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonDistanceMetric Context triple: [KNN, commonDistanceMetric, Euclidean distance]
-
A.
distanceMetric
chosen
Indicates a quantitative measure of how far apart two entities are within a given space or according to a specified metric.
-
B.
distanceCharacteristic
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
C.
cityBlock
Indicates that one entity is a city block that contains, is the location of, or is otherwise spatially associated with the other entity.
-
D.
numberOfDistances
Indicates the count of distinct distance values associated with or measured between entities in a given context.
-
E.
distanceMeasurementMethod
Indicates the method or technique used to determine or measure the distance between entities.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5605f081908367bd08ab1ec9ab |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.