Triple

T179419
Position Surface form Disambiguated ID Type / Status
Subject implicit function theorem E3650 entity
Predicate hasApplication P1129 FINISHED
Object defining smooth submanifolds as level sets 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: defining smooth submanifolds as level sets | Statement: [implicit function theorem, hasApplication, defining smooth submanifolds as level sets]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApplication
Context triple: [implicit function theorem, hasApplication, defining smooth submanifolds as level sets]
  • A. appliesTo chosen
    Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
  • B. appliedBy
    Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
  • C. appliesAt
    Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
  • D. hasSupported
    Indicates that one entity has provided assistance, endorsement, or backing to another entity, either materially, emotionally, or through advocacy.
  • E. hasFeature
    Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
  • 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_69a25374990081909766d30c79a18e0e completed Feb. 28, 2026, 2:31 a.m.
NER Named-entity recognition batch_69a25900709c8190a65e778936be5dd5 completed Feb. 28, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69a2566b53d481909c0ed40dd3719e8c completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:39 a.m.