Triple
T22328566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fubini–Study form |
E551964
|
entity |
| Predicate | isNormalizedSoThat |
P127763
|
FINISHED |
| Object | integral over CP^1 equals π |
—
|
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: integral over CP^1 equals π | Statement: [Fubini–Study form, isNormalizedSoThat, integral over CP^1 equals π]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNormalizedSoThat Context triple: [Fubini–Study form, isNormalizedSoThat, integral over CP^1 equals π]
-
A.
usesNormalization
Indicates that one entity applies or relies on a normalization process or technique in relation to another entity or data.
-
B.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
-
C.
normIs
Indicates that something conforms to, or is characterized by, a particular standard, rule, or norm.
-
D.
isNormalIn
Indicates that one group is a normal subgroup of another group, meaning it is invariant under conjugation by elements of the larger group.
-
E.
normalizationType
chosen
Indicates the specific method or scheme used to normalize or standardize data, values, or representations within a given context.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15769fdb48190b84e0c019ab63579 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.