Triple
T36640352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL(2,7) |
E904566
|
entity |
| Predicate | isNonSolvable |
P186110
|
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: [SL(2,7), isNonSolvable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonSolvable Context triple: [SL(2,7), isNonSolvable, 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.
admitsSolution
Indicates that a problem, system, or situation allows for or possesses at least one valid solution.
-
D.
tractableOn
Indicates that a problem, task, or situation can be effectively handled, solved, or managed under the specified conditions or by the specified method.
-
E.
hasPathologicalSolutions
Indicates that the relationship or action involves the existence of abnormal, counterintuitive, or non-standard solutions that violate typical expectations or regularity conditions.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.