Triple
T11919092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitting ideal |
E283606
|
entity |
| Predicate | inAlgebraicGeometry |
P102353
|
FINISHED |
| Object | defines closed subschemes |
—
|
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: defines closed subschemes | Statement: [Fitting ideal, inAlgebraicGeometry, defines closed subschemes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inAlgebraicGeometry Context triple: [Fitting ideal, inAlgebraicGeometry, defines closed subschemes]
-
A.
isRingTheoreticAnalogueOf
Indicates that one concept in ring theory serves as the structural or conceptual counterpart of another notion from a different mathematical context.
-
B.
arePolynomialsIn
Indicates that the specified expressions are polynomials in the given variable(s) or over the given ring/field.
-
C.
canonicalVarieties
Indicates that one entity is a canonical or standard variety/form of another entity within a given classification or system.
-
D.
algebra
Indicates a relationship involving algebraic operations, structures, or properties between mathematical entities.
-
E.
closedSubsetsOfAffineSpace
Indicates that the related entities are subsets of an affine space that are closed in the corresponding topology.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8dff77481908cacf6ad03df34ac |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:44 p.m.