Triple
T34156650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plancherel theorem for locally compact abelian groups |
E876155
|
entity |
| Predicate | codomainSpace |
P7031
|
FINISHED |
| Object | L2(Ĝ) |
—
|
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(Ĝ) | Statement: [Plancherel theorem for locally compact abelian groups, codomainSpace, L2(Ĝ)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codomainSpace Context triple: [Plancherel theorem for locally compact abelian groups, codomainSpace, L2(Ĝ)]
-
A.
codomain
chosen
Indicates the set of all possible output values that a function or mapping can produce, regardless of which values are actually attained.
-
B.
categoryCodomain
Indicates that something belongs to, or is classified within, the codomain category of a given mapping or function.
-
C.
coordinateDomain
Indicates that two or more entities share the same coordinate system or spatial reference framework for describing positions.
-
D.
naturalDomain
Indicates that something inherently belongs to or operates within a particular domain, scope, or area of applicability.
-
E.
outputDomain
Indicates the type or range of values that can be produced as the result of a function, process, or system.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb6ba808190af28fe23e8bc52bf |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.