Triple
T20836514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cook–Levin theorem |
E512972
|
entity |
| Predicate | concernsDecisionProblems |
P132452
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cook–Levin theorem, concernsDecisionProblems, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsDecisionProblems Context triple: [Cook–Levin theorem, concernsDecisionProblems, yes]
-
A.
decisionsConcern
Indicates that certain decisions are about, relate to, or focus on a particular subject, issue, or entity.
-
B.
decisionProblem
chosen
Indicates that the subject is a computational problem for which the task is to decide, with a yes/no answer, whether given inputs satisfy a specified condition.
-
C.
decidability
Indicates whether a given problem, property, or statement can be algorithmically determined to be true or false for all possible inputs.
-
D.
openProblemIn
Indicates that a particular problem or issue is currently active or unresolved within a specified context, domain, or environment.
-
E.
concernsProblem
Indicates that something is about, related to, or deals with a particular problem or issue.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c326daec8190bd4caa41a4b38833 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:42 p.m.