Triple
T29096310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNA computing |
E735011
|
entity |
| Predicate | canSolve |
P8791
|
FINISHED |
| Object | NP-hard problems |
—
|
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: NP-hard problems | Statement: [DNA computing, canSolve, NP-hard problems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSolve Context triple: [DNA computing, canSolve, NP-hard problems]
-
A.
canBeSolvable
Indicates that a problem, situation, or condition has the potential to be resolved or successfully solved under some circumstances.
-
B.
providesSolutionFor
Indicates that one entity offers or supplies a remedy, answer, or resolution to a problem, need, or issue associated with another entity.
-
C.
admitsSolution
Indicates that a problem, system, or situation allows for or possesses at least one valid solution.
-
D.
problemTypeSolved
Indicates that a given problem has been successfully solved or resolved by a particular entity or method.
-
E.
commonlySolvedBy
chosen
Indicates that a problem, task, or issue is typically addressed or resolved through a particular method, tool, or agent.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6618129b08190ac4bbb0cd24d957c |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:09 a.m.