Triple
T15244888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIP = NEXP |
E364352
|
entity |
| Predicate | assumesProversAre |
P1458
|
FINISHED |
| Object | computationally unbounded |
—
|
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: computationally unbounded | Statement: [MIP = NEXP, assumesProversAre, computationally unbounded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assumesProversAre Context triple: [MIP = NEXP, assumesProversAre, computationally unbounded]
-
A.
assumes
chosen
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
B.
isAssumedIn
Indicates that something is taken for granted or presumed to hold within a particular context, without requiring explicit proof or verification.
-
C.
assumedRuleOf
Indicates that one entity is presumed or taken to hold authoritative control, governance, or dominion over another entity, typically without definitive confirmation.
-
D.
usesProofLanguage
Indicates that one entity employs a specific formal or structured language to express or present a proof related to another entity.
-
E.
partiallyProvenFor
Indicates that something has been shown to hold or be true for part of a domain or set of cases, but not yet for all cases.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f306f08190be448b215d6c9b6c |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.