Triple

T13035747
Position Surface form Disambiguated ID Type / Status
Subject Monge problem in optimal transport E326555 entity
Predicate hasContinuousVersion P107556 FINISHED
Object Monge problem on continuous probability measures 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: Monge problem on continuous probability measures | Statement: [Monge problem in optimal transport, hasContinuousVersion, Monge problem on continuous probability measures]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasContinuousVersion
Context triple: [Monge problem in optimal transport, hasContinuousVersion, Monge problem on continuous probability measures]
  • A. continuousVersionName
    Indicates that one entity is the name or label assigned to a continuous or ongoing version of another entity.
  • B. hasLiveVersions
    Indicates that an entity has one or more recorded or documented live-performance versions of itself.
  • C. hasVersionIn
    Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
  • D. hasVersionStatus
    Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
  • E. hasMultipleVersions
    Indicates that an entity exists in more than one distinct version or revision.
  • 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_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.
PDg Predicate description generation batch_69d97e3df2288190a7f27d31d248bb7f completed April 10, 2026, 10:48 p.m.
Created at: April 9, 2026, 8:55 p.m.