Triple
T27133867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontryagin duality |
E681628
|
entity |
| Predicate | domainCategory |
P87
|
FINISHED |
| Object | category of locally compact abelian groups |
—
|
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: category of locally compact abelian groups | Statement: [Pontryagin duality, domainCategory, category of locally compact abelian groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainCategory Context triple: [Pontryagin duality, domainCategory, category of locally compact abelian groups]
-
A.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
-
B.
socialCategory
Indicates that an entity belongs to, or is classified within, a particular social group, class, or category.
-
C.
commonsCategory
Indicates that an entity is associated with a specific media or topic category on Wikimedia Commons.
-
D.
textCategory
Indicates that a piece of text belongs to or is classified under a particular category or type.
-
E.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62478fd0c81909b7de1d72aa0e2c0 |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:06 a.m.