Triple
T37258726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gel'fand–Kirillov conjecture |
E924201
|
entity |
| Predicate | knownToFailFor |
P30122
|
FINISHED |
| Object | some simple Lie algebras |
—
|
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: some simple Lie algebras | Statement: [Gel'fand–Kirillov conjecture, knownToFailFor, some simple Lie algebras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownToFailFor Context triple: [Gel'fand–Kirillov conjecture, knownToFailFor, some simple Lie algebras]
-
A.
failsInGeneralFor
Indicates that an action, method, or approach does not succeed under typical or broad conditions, rather than only in specific edge cases.
-
B.
failsTo
Indicates that an expected action, process, or condition does not successfully occur or is not fulfilled.
-
C.
failsWhen
Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
-
D.
typeOfFailure
Indicates the specific kind or category of failure that occurred in relation to an entity or process.
-
E.
failedOn
chosen
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:15 p.m.