Triple

T29464851
Position Surface form Disambiguated ID Type / Status
Subject Riesz projection E747348 entity
Predicate isWellDefinedIf P96505 FINISHED
Object Γ lies in the resolvent set of T 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: Γ lies in the resolvent set of T | Statement: [Riesz projection, isWellDefinedIf, Γ lies in the resolvent set of T]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isWellDefinedIf
Context triple: [Riesz projection, isWellDefinedIf, Γ lies in the resolvent set of T]
  • A. areDefinedIn
    Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
  • B. isWellOrdered
    Indicates that a set is equipped with a total order in which every non-empty subset has a least element.
  • C. wasDefinedBy
    Indicates that something was formally specified, described, or established by a particular agent, source, or defining entity.
  • D. canBeDefinedFor chosen
    Indicates that a certain concept, operation, or property is applicable to and can be meaningfully specified for a given entity or set of entities.
  • E. isWellEstablished
    Indicates that something has been firmly recognized, accepted, or validated over time as reliable or authoritative.
  • 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_69f0bd4125f88190b56104591351619c completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66ba6316c8190a84523b9bd642e9a completed May 2, 2026, 9:24 p.m.
PD Predicate disambiguation batch_69f66339175c819080bd70f0ff7057b1 completed May 2, 2026, 8:48 p.m.
Created at: April 28, 2026, 3:52 p.m.