Triple

T11084458
Position Surface form Disambiguated ID Type / Status
Subject Dynkin formula E262081 entity
Predicate typicalCondition P7027 FINISHED
Object bounded stopping time or suitable integrability 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: bounded stopping time or suitable integrability | Statement: [Dynkin formula, typicalCondition, bounded stopping time or suitable integrability]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalCondition
Context triple: [Dynkin formula, typicalCondition, bounded stopping time or suitable integrability]
  • A. hasTypicalConditions
    Indicates that something is associated with conditions or circumstances that are commonly or normally present for it.
  • B. typicalCircumstance
    Indicates the usual or commonly occurring situation, condition, or context in which an event, action, or relationship typically takes place.
  • C. typicalIn
    Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
  • D. globalCondition
    Indicates that a condition applies universally or system-wide rather than being limited to a specific local context or subset.
  • E. typicalAssumption chosen
    Indicates that something is taken as a standard or default assumption that generally holds in typical or normal circumstances.
  • 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_69d6aa9983c08190b0ef61603b69feac completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d799c0cc3081908448cfb26c08daf5 completed April 9, 2026, 12:21 p.m.
PD Predicate disambiguation batch_69d744185a5881909ba4cf151d1798ec completed April 9, 2026, 6:15 a.m.
Created at: April 8, 2026, 9:27 p.m.