Triple
T1422255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OWL Full |
E30248
|
entity |
| Predicate | hasReasoningComplexity |
P28909
|
FINISHED |
| Object | undecidable in general |
—
|
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: undecidable in general | Statement: [OWL Full, hasReasoningComplexity, undecidable in general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReasoningComplexity Context triple: [OWL Full, hasReasoningComplexity, undecidable in general]
-
A.
hasCognitiveComponent
Indicates that the related entity or process involves or depends on mental activities such as thinking, reasoning, perception, or understanding.
-
B.
reasoningIncludes
Indicates that a reasoning process or argument explicitly incorporates or makes use of the referenced element as one of its components or steps.
-
C.
intelligenceLevel
Indicates the degree or measure of cognitive ability or intelligence attributed to an entity.
-
D.
typeOfIntelligence
Indicates that one entity is a specific kind or category of intelligence in relation to another entity.
-
E.
timeComplexity
Indicates the computational growth rate of an algorithm’s resource usage (typically time) as a function of input size.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c52e4ed881908d85e0cb9fe851ac |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c4752abc8190a33b634c4d6fad28 |
completed | March 1, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69a4c52bbb748190aaa804438d31f4c2 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8 p.m.