Triple

T3044197
Position Surface form Disambiguated ID Type / Status
Subject Tucker’s lemma E83404 entity
Predicate hasConclusion P44778 FINISHED
Object existence of an edge whose endpoints have opposite labels 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: existence of an edge whose endpoints have opposite labels | Statement: [Tucker’s lemma, hasConclusion, existence of an edge whose endpoints have opposite labels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasConclusion
Context triple: [Tucker’s lemma, hasConclusion, existence of an edge whose endpoints have opposite labels]
  • A. concludedThat
    Indicates that one entity has reached or stated a judgment, inference, or decision about a proposition or situation involving another entity.
  • B. canConclude
    Indicates that one entity is able to logically derive or reach a conclusion about another entity or situation.
  • C. concludedWith
    Indicates that an event, process, or interaction ended or was finalized by a specific outcome, action, or state.
  • D. concluded
    Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
  • E. concludedBy
    Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
  • 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_69ad8b24924c8190a9bb6f61d519e4ae completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9b5ec5988190b8b6c95c743c6d1e completed March 8, 2026, 3:53 p.m.
PD Predicate disambiguation batch_69ad961fc62c819087c4c3a44b00847d completed March 8, 2026, 3:30 p.m.
PDg Predicate description generation batch_69ad97f6af3881909f4547967384114c completed March 8, 2026, 3:38 p.m.
Created at: March 8, 2026, 3:01 p.m.