Triple
T32790007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gröbner fan |
E838598
|
entity |
| Predicate | relatesTermOrdersVia |
P195598
|
FINISHED |
| Object | adjacency of Gröbner cones |
—
|
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: adjacency of Gröbner cones | Statement: [Gröbner fan, relatesTermOrdersVia, adjacency of Gröbner cones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesTermOrdersVia Context triple: [Gröbner fan, relatesTermOrdersVia, adjacency of Gröbner cones]
-
A.
relatedToTerm
Indicates a general, non-specific relationship or association between one term and another.
-
B.
establishesRelationsBetween
Indicates that one entity creates, initiates, or formalizes a connection or association between two or more other entities.
-
C.
refersToOrder
Indicates that one entity makes reference to, or is associated with, a specific order.
-
D.
confersOrder
Indicates that one entity formally bestows or grants an order, rank, or honorific distinction upon another entity.
-
E.
linkedOrder
chosen
Indicates that one order is associated with or connected to another order in a defined relationship.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:14 a.m.