Triple
T34533325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bose–Mesner algebra |
E886600
|
entity |
| Predicate | hasDualBasis |
P179663
|
FINISHED |
| Object | primitive idempotent basis |
—
|
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: primitive idempotent basis | Statement: [Bose–Mesner algebra, hasDualBasis, primitive idempotent basis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDualBasis Context triple: [Bose–Mesner algebra, hasDualBasis, primitive idempotent basis]
-
A.
hasDualSpace
Indicates that one mathematical space is the dual space consisting of all linear functionals defined on another space.
-
B.
hasAlternativeBasis
Indicates that something is supported, justified, or founded on a different underlying reason, source, or principle than the primary or original one.
-
C.
hasBasisIn
Indicates that one entity is founded, derived, or justified on the grounds of another entity.
-
D.
hasStandardBasis
Indicates that a given vector space is equipped with or possesses its usual canonical set of basis vectors.
-
E.
haveDualityProperty
Indicates that an entity possesses a characteristic or state that inherently consists of two complementary, contrasting, or coexisting aspects.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:02 a.m.