Triple
T6371005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halting problem |
E143342
|
entity |
| Predicate | solutionSet |
P3643
|
FINISHED |
| Object | recursively enumerable but not recursive |
—
|
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: recursively enumerable but not recursive | Statement: [Halting problem, solutionSet, recursively enumerable but not recursive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solutionSet Context triple: [Halting problem, solutionSet, recursively enumerable but not recursive]
-
A.
solutionType
Indicates the specific category or kind of solution associated with an entity or problem.
-
B.
isSolutionOf
Indicates that one entity is a correct answer or satisfies the conditions of a given problem, equation, or task.
-
C.
admitsSolution
chosen
Indicates that a problem, system, or situation allows for or possesses at least one valid solution.
-
D.
solved
Indicates that one entity has successfully found a solution or answer to a problem, task, or challenge involving another entity.
-
E.
providesSolutionFor
Indicates that one entity offers or supplies a remedy, answer, or resolution to a problem, need, or issue associated with 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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068289eac8190a17affed87340c1f |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.