Triple
T11411814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gelfand triple |
E270387
|
entity |
| Predicate | hasDual |
P31338
|
FINISHED |
| Object | continuous dual space Φ′ of Φ |
—
|
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: continuous dual space Φ′ of Φ | Statement: [Gelfand triple, hasDual, continuous dual space Φ′ of Φ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDual Context triple: [Gelfand triple, hasDual, continuous dual space Φ′ of Φ]
-
A.
haveDualityProperty
Indicates that an entity possesses a characteristic or state that inherently consists of two complementary, contrasting, or coexisting aspects.
-
B.
dualPair
chosen
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
C.
dualLicensed
Indicates that an entity is simultaneously licensed under two distinct licenses or licensing regimes.
-
D.
hasTwinFeature
Indicates that two entities share an identical or nearly identical feature, characteristic, or component, as if they are twins in that respect.
-
E.
hasDouble
Indicates that an entity possesses or is associated with a counterpart that is a duplicate or closely similar version of it.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8015017d08190b4020c76545556d6 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.