Triple
T10732793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serre duality |
E253115
|
entity |
| Predicate | dimensionCondition |
P73086
|
FINISHED |
| Object | n = dim X |
—
|
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: n = dim X | Statement: [Serre duality, dimensionCondition, n = dim X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dimensionCondition Context triple: [Serre duality, dimensionCondition, n = dim X]
-
A.
dimensionRestriction
Indicates a constraint or limit imposed on the size, extent, or number of dimensions associated with an entity or relationship.
-
B.
dimensionStatement
chosen
Indicates that a statement specifies the measured size, extent, or dimensional properties of an entity or relationship.
-
C.
angleCondition
Indicates that a specified geometric relationship holds between angles, such as equality, inequality, or a particular angular constraint.
-
D.
dimensionType
Indicates the specific kind or category of dimension that characterizes how something is measured or structured.
-
E.
dimensionVariant
Indicates a relationship where one entity is a variant or alternative version of another with respect to certain dimensions or configurable attributes.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7101ff9808190a27fcc06da097ea3 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.