Triple
T31024359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cohen–Macaulay ring |
E790527
|
entity |
| Predicate | isStableUnder |
P172200
|
FINISHED |
| Object | localization |
—
|
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: localization | Statement: [Cohen–Macaulay ring, isStableUnder, localization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStableUnder Context triple: [Cohen–Macaulay ring, isStableUnder, localization]
-
A.
isStable
Indicates that the state, condition, or configuration of an entity does not change significantly over time or under expected variations in its environment.
-
B.
isConditionallyStable
Indicates that an entity remains stable only under certain specified conditions or constraints.
-
C.
stabilizedBy
Indicates that an entity’s state, structure, or behavior is made more steady, secure, or resistant to change through the influence or support of another entity.
-
D.
haveStabilityDeterminedBy
Indicates that the stability of one entity is determined or governed by another specified factor or entity.
-
E.
isMetastable
Indicates that a state or configuration is temporarily stable but can transition to a more stable state under small perturbations or over time.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 29, 2026, 8:58 p.m.