Triple

T20627407
Position Surface form Disambiguated ID Type / Status
Subject Nevanlinna–Pick interpolation E506854 entity
Predicate existenceCriterion P67472 FINISHED
Object positivity of the Pick matrix 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: positivity of the Pick matrix | Statement: [Nevanlinna–Pick interpolation, existenceCriterion, positivity of the Pick matrix]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: existenceCriterion
Context triple: [Nevanlinna–Pick interpolation, existenceCriterion, positivity of the Pick matrix]
  • A. existsIf chosen
    Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
  • B. existsAs
    Indicates that one entity has the same identity or manifestation as another, effectively asserting they are the same existing thing or state.
  • C. existenceScope
    Indicates the contextual or situational bounds within which an entity or condition is considered to exist or hold true.
  • D. existsWithin
    Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
  • E. existsFor
    Indicates that something is present, available, or holds true for a particular entity, context, or condition.
  • 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_69e0b4bd4a0081908d4e97a590a33fb2 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6abe645888190b639ebedc5b3041a completed April 20, 2026, 10:42 p.m.
PD Predicate disambiguation batch_69e5a00c43308190b7ea58d559257e07 completed April 20, 2026, 3:39 a.m.
Created at: April 16, 2026, 11:42 a.m.