Triple

T34156649
Position Surface form Disambiguated ID Type / Status
Subject Plancherel theorem for locally compact abelian groups E876155 entity
Predicate domainSpace P178449 FINISHED
Object L2(G) 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: L2(G) | Statement: [Plancherel theorem for locally compact abelian groups, domainSpace, L2(G)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: domainSpace
Context triple: [Plancherel theorem for locally compact abelian groups, domainSpace, L2(G)]
  • A. namedSpace
    Indicates that an entity has been assigned or is associated with a specific name within a particular namespace or naming context.
  • B. spaceDomain
    Indicates that the relationship or activity occurs within, pertains to, or is governed by the space domain (outer space and related space operations).
  • C. domainServed
    Indicates that a particular domain or area is supported, covered, or provided for by a given entity or service.
  • D. partOfDomain
    Indicates that one entity belongs to, is included within, or is a constituent part of the scope or domain defined by another entity.
  • E. domainOfq
    Indicates that a given entity serves as the domain (set of permissible inputs or arguments) for the quantity or relation denoted by q.
  • 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_69f349ac987481908a8e6053f665bc8b completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7107acf0481909b01467b9ebbde01 completed May 3, 2026, 9:08 a.m.
PD Predicate disambiguation batch_69f70f3a54d481909ba6bdda3647b761 completed May 3, 2026, 9:02 a.m.
PDg Predicate description generation batch_69f70fb41a9c8190a121e62e510dc18a completed May 3, 2026, 9:04 a.m.
Created at: May 1, 2026, 1:54 a.m.