Triple
T9297152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auslander–Buchsbaum formula |
E223665
|
entity |
| Predicate | involvesRing |
P66253
|
FINISHED |
| Object | local ring (R, m) |
—
|
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: local ring (R, m) | Statement: [Auslander–Buchsbaum formula, involvesRing, local ring (R, m)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesRing Context triple: [Auslander–Buchsbaum formula, involvesRing, local ring (R, m)]
-
A.
hasRing
Indicates that one entity possesses, wears, or is characterized by the presence of a ring.
-
B.
ringType
chosen
Indicates the specific kind or category of ring associated with an entity or relationship.
-
C.
ringsOn
Indicates that one entity encircles or forms a ring around another entity, typically by being placed around it.
-
D.
ringsBy
Indicates that one entity creates or designs rings that are associated with, produced by, or attributed to another entity.
-
E.
hasRingComposition
Indicates that one entity is composed of, or structurally organized around, a ring-like arrangement or circular structure.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd089e3ae88190aa4181cdd85a67b8 |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.