Triple
T20509513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heisenberg Lie algebra |
E503521
|
entity |
| Predicate | isSolvable |
P3643
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Heisenberg Lie algebra, isSolvable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSolvable Context triple: [Heisenberg Lie algebra, isSolvable, true]
-
A.
canBeSolvable
Indicates that a problem, situation, or condition has the potential to be resolved or successfully solved under some circumstances.
-
B.
isExactlySolvable
Indicates that a problem, model, or equation can be solved completely and exactly (without approximation) using known analytical or algorithmic methods.
-
C.
isSolutionOf
Indicates that one entity is a correct answer or satisfies the conditions of a given problem, equation, or task.
-
D.
admitsSolution
chosen
Indicates that a problem, system, or situation allows for or possesses at least one valid solution.
-
E.
hasFiniteNumberOfSolutions
Indicates that the related equation, system, or problem has only a limited, countable set of distinct solutions, rather than infinitely many or none.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dc9de788190882ce471966ef2b4 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.