Triple
T20836507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cook–Levin theorem |
E512972
|
entity |
| Predicate | problemTypeInvolved |
P83422
|
FINISHED |
| Object | Boolean satisfiability problem |
—
|
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: Boolean satisfiability problem | Statement: [Cook–Levin theorem, problemTypeInvolved, Boolean satisfiability problem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: problemTypeInvolved Context triple: [Cook–Levin theorem, problemTypeInvolved, Boolean satisfiability problem]
-
A.
problemType
chosen
Indicates the specific category or classification of a problem within a defined problem space or system.
-
B.
problemTypeSolved
Indicates that a given problem has been successfully solved or resolved by a particular entity or method.
-
C.
typicalProblem
Indicates that a situation, issue, or obstacle is representative or characteristic of the usual problems encountered in a given context.
-
D.
problemStatement
Indicates that an entity presents, defines, or expresses a specific problem or issue to be addressed.
-
E.
correctedProblem
Indicates that one entity has fixed or amended an error or issue present in another entity.
- 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.