Triple
T8060616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M language |
E188108
|
entity |
| Predicate | isTuringComplete |
P26986
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [M language, isTuringComplete, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTuringComplete Context triple: [M language, isTuringComplete, true]
-
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.
isTotallyComplex
Indicates that something possesses a level of complexity that is complete, multifaceted, and not reducible to simpler or purely real/straightforward components.
-
C.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
D.
isT1
Indicates that one entity is classified or designated as type T1 in relation to another entity or context.
-
E.
hasTerminalFunction
Indicates that something possesses a function or role specifically associated with an endpoint, boundary, or final stage within a system or process.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fcc61c0819085edc26e75c5f6d5 |
completed | March 31, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:26 p.m.