Triple
T9297153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auslander–Buchsbaum formula |
E223665
|
entity |
| Predicate | involvesIdeal |
P1393
|
FINISHED |
| Object | maximal ideal m of R |
—
|
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: maximal ideal m of R | Statement: [Auslander–Buchsbaum formula, involvesIdeal, maximal ideal m of R]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesIdeal Context triple: [Auslander–Buchsbaum formula, involvesIdeal, maximal ideal m of R]
-
A.
coreIdeal
Indicates that something is a fundamental, central principle or value that defines or strongly guides another entity.
-
B.
hasIdeal
Indicates that an entity holds or is associated with a guiding principle, standard, or value it considers perfect or most desirable.
-
C.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
D.
hasIdealization
Indicates that one entity is a simplified, abstracted, or ideal form or model of another entity, capturing its essential features while omitting complexities.
-
E.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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.