Triple
T1483724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game of Life |
E29416
|
entity |
| Predicate | computationalClass |
P29141
|
FINISHED |
| Object | 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: Turing complete | Statement: [Game of Life, computationalClass, Turing complete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computationalClass Context triple: [Game of Life, computationalClass, Turing complete]
-
A.
computes
Indicates that one entity performs a calculation or processing operation to produce a result from given data or inputs.
-
B.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
C.
trainingCompute
Indicates the amount or configuration of computational resources used to train a model or system.
-
D.
turingComplete
Indicates that a system or language is capable of performing any computation that a universal Turing machine can, given enough time and memory.
-
E.
researchClassification
Indicates that an entity is assigned a specific category or type within a research-related classification scheme.
- F. None of above. chosen
Provenance (4 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c679714c8190ac53630fb49e19c5 |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52bbb748190aaa804438d31f4c2 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8:12 p.m.