Triple

T15918509
Position Surface form Disambiguated ID Type / Status
Subject Happy Ending problem E386030 entity
Predicate typicalExampleOf P108356 FINISHED
Object classical problem in extremal combinatorics 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: classical problem in extremal combinatorics | Statement: [Happy Ending problem, typicalExampleOf, classical problem in extremal combinatorics]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalExampleOf
Context triple: [Happy Ending problem, typicalExampleOf, classical problem in extremal combinatorics]
  • A. typicalIn
    Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
  • B. exampleType
    Indicates that one entity serves as a representative or illustrative instance of the type or category defined by another entity.
  • C. usedAsExampleIn
    Indicates that one entity is cited or presented as an illustrative example within another entity, such as a text, discussion, or explanation.
  • D. typicalItem
    Indicates that an item is a representative or characteristic example of a broader category, class, or set.
  • E. standardExample chosen
    Indicates that something is a typical or canonical instance used to illustrate a general case or concept.
  • 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_69d86da686e4819097cbf3b1fc2d881d completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e172b48b308190bc430b2308cbc75b completed April 16, 2026, 11:37 p.m.
PD Predicate disambiguation batch_69e142cf5c548190a931f7b58144cd31 completed April 16, 2026, 8:13 p.m.
Created at: April 10, 2026, 4:52 a.m.