Triple

T11016749
Position Surface form Disambiguated ID Type / Status
Subject Catmull–Rom spline E260383 entity
Predicate typicalParameterization P89639 FINISHED
Object uniform parameterization 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: uniform parameterization | Statement: [Catmull–Rom spline, typicalParameterization, uniform parameterization]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalParameterization
Context triple: [Catmull–Rom spline, typicalParameterization, uniform parameterization]
  • A. typicalMapping
    Indicates a standard or commonly used correspondence between elements of one set, structure, or representation and those of another.
  • B. hasParameterization chosen
    Indicates that one entity serves as the specific parameterization or parameter-setting scheme used to define or configure another entity.
  • C. typicalTopology
    Indicates the usual or most common network or structural arrangement that characterizes how the related entities are organized or interconnected.
  • D. typicalSymbol
    Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
  • E. standardPar
    Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
  • 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_69d6aa9687448190b28d353b1b6a610e completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d797a682908190b061d1995e2866b6 completed April 9, 2026, 12:12 p.m.
PD Predicate disambiguation batch_69d72e96be6c8190a46c69f61b2d8cd4 completed April 9, 2026, 4:44 a.m.
Created at: April 8, 2026, 9:25 p.m.