Triple

T13035720
Position Surface form Disambiguated ID Type / Status
Subject Monge problem in optimal transport E326555 entity
Predicate typicalCostFunction P42790 FINISHED
Object squared 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: squared Euclidean distance | Statement: [Monge problem in optimal transport, typicalCostFunction, squared Euclidean distance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalCostFunction
Context triple: [Monge problem in optimal transport, typicalCostFunction, squared Euclidean distance]
  • A. computationalCost
    Indicates the amount of computing resources (such as time, memory, or processing power) required to perform a given operation or process.
  • B. typicalFunction chosen
    Indicates that something serves as the usual or characteristic function or role of an entity.
  • C. costModel
    Indicates the pricing or cost-structure relationship applied to an entity, defining how its costs are calculated or charged.
  • D. estimatedCost
    Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
  • E. reducedCostOf
    Indicates that one entity represents a lowered or discounted cost associated with another entity, typically compared to a standard or original price.
  • 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_69d8076cc45c81908123123f43e69266 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97f2a71a0819098bb6cf8a4b2208a completed April 10, 2026, 10:52 p.m.
PD Predicate disambiguation batch_69d97dc39a0881908119c62e31bf6182 completed April 10, 2026, 10:46 p.m.
Created at: April 9, 2026, 8:55 p.m.