Triple
T32789980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gröbner fan |
E838598
|
entity |
| Predicate | dimensionOfConesDependsOn |
P175118
|
FINISHED |
| Object | number of variables in the polynomial ring |
—
|
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: number of variables in the polynomial ring | Statement: [Gröbner fan, dimensionOfConesDependsOn, number of variables in the polynomial ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dimensionOfConesDependsOn Context triple: [Gröbner fan, dimensionOfConesDependsOn, number of variables in the polynomial ring]
-
A.
hasCone
Indicates that one entity possesses, is equipped with, or is characterized by a cone or cone-shaped component.
-
B.
hasMultipleCones
Indicates that an entity is associated with more than one cone-shaped object or structure.
-
C.
hasEndCones
Indicates that an object possesses cone-shaped elements at one or both of its ends.
-
D.
hasConeType
Indicates that an entity possesses or is associated with a specific type or category of cone.
-
E.
coneType
Indicates the specific category or style of cone associated with an entity (e.g., type, shape, or design of the cone).
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6ce6c76bc8190b865343d3f5810c9 |
completed | May 3, 2026, 4:26 a.m. |
Created at: May 1, 2026, 1:14 a.m.