Triple

T25432909
Position Surface form Disambiguated ID Type / Status
Subject Hurwitz theorem E637304 entity
Predicate extremalCase P17815 FINISHED
Object golden ratio 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: golden ratio | Statement: [Hurwitz theorem, extremalCase, golden ratio]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: extremalCase
Context triple: [Hurwitz theorem, extremalCase, golden ratio]
  • A. isExtremalWhen chosen
    Indicates that a given entity or configuration attains an extreme value (such as a maximum or minimum) of some specified quantity or property under certain conditions.
  • B. extremalFunction
    Indicates that a function attains an extreme value (such as a minimum or maximum) under given conditions or over a specified domain.
  • C. typicalExtremalFamily
    Indicates that a given family of objects (such as sets or structures) exemplifies the standard or characteristic configuration that achieves an extremal bound in a particular combinatorial or optimization problem.
  • D. hasExtremePoint
    Indicates that one entity possesses or includes another entity that is an extreme (e.g., maximum or minimum) point within its structure or boundary.
  • E. boundaryCase
    Indicates that one entity represents a limiting or extreme condition used to test or define the valid range or behavior of another entity.
  • 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_69e75db58a1c8190891b9ff7c2f8414e completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f6dc7d088190b1e4c191172ea256 completed May 2, 2026, 1:06 p.m.
PD Predicate disambiguation batch_69f4683b34748190818428489a226124 completed May 1, 2026, 8:45 a.m.
Created at: April 21, 2026, 1:58 p.m.