Triple

T13894151
Position Surface form Disambiguated ID Type / Status
Subject Hadamard’s example of ill-posed problems E334044 entity
Predicate failsProperty P111916 FINISHED
Object uniqueness or stability in the usual sense 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: uniqueness or stability in the usual sense | Statement: [Hadamard’s example of ill-posed problems, failsProperty, uniqueness or stability in the usual sense]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: failsProperty
Context triple: [Hadamard’s example of ill-posed problems, failsProperty, uniqueness or stability in the usual sense]
  • A. failedOn
    Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
  • B. failsToConformTo
    Indicates that one entity does not meet, match, or comply with the standards, rules, or expectations defined by another entity or specification.
  • C. failureBehavior
    Indicates how a system, component, or process is expected to respond or act when a failure or error condition occurs.
  • D. failsWhen
    Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
  • E. failsAtFirst
    Indicates that an attempt at an action or task does not succeed on the first try.
  • F. None of above. chosen

Provenance (4 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de23a741908190bdf46d76c5f1411a completed April 14, 2026, 11:23 a.m.
PD Predicate disambiguation batch_69dd464b1ab48190ae50bfc902bf6ef7 completed April 13, 2026, 7:38 p.m.
PDg Predicate description generation batch_69de01ed2098819088ec45069f6f2609 completed April 14, 2026, 8:59 a.m.
Created at: April 9, 2026, 10:15 p.m.