Triple

T3913070
Position Surface form Disambiguated ID Type / Status
Subject axiom of choice E87367 entity
Predicate controversialBecause P52533 FINISHED
Object leads to non-constructive existence proofs 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: leads to non-constructive existence proofs | Statement: [axiom of choice, controversialBecause, leads to non-constructive existence proofs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: controversialBecause
Context triple: [axiom of choice, controversialBecause, leads to non-constructive existence proofs]
  • A. controversy
    Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
  • B. controversyType
    Indicates the specific kind or category of controversy associated with an entity or situation.
  • C. roleInControversy
    Indicates the specific part, involvement, or function an entity has within a particular controversy or disputed situation.
  • D. locationOfControversy
    Indicates the place or setting where a dispute, debate, or controversy occurs or is centered.
  • E. contestedBy
    Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
  • 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_69aed9424514819086e9c58adde6652d completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aef188b474819087680db42b04ecdd completed March 9, 2026, 4:12 p.m.
PD Predicate disambiguation batch_69aee75eedcc81908088ff4dbb8be56b completed March 9, 2026, 3:29 p.m.
PDg Predicate description generation batch_69aef18748648190b85e62f7796ff4b4 completed March 9, 2026, 4:12 p.m.
Created at: March 9, 2026, 3:22 p.m.