Triple
T27639027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Script |
E696538
|
entity |
| Predicate | turingCompleteness |
P26986
|
FINISHED |
| Object | not Turing-complete |
—
|
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: not Turing-complete | Statement: [Bitcoin Script, turingCompleteness, not Turing-complete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turingCompleteness Context triple: [Bitcoin Script, turingCompleteness, not Turing-complete]
-
A.
turingComplete
chosen
Indicates that a system or language is capable of performing any computation that a universal Turing machine can, given enough time and memory.
-
B.
computabilityRequirement
Indicates that something must be capable of being computed or effectively carried out by an algorithm or computational process.
-
C.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
D.
isNPComplete
Indicates that a decision problem is both in NP and NP-hard, meaning it can be verified in polynomial time and is at least as hard as any problem in NP.
-
E.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6318fec0c8190971b4fc1a7df10d3 |
completed | May 2, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:25 p.m.