Triple
T3522557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCP theorem |
E74456
|
entity |
| Predicate | relatedTheorem |
P49212
|
FINISHED |
| Object | IP equals PSPACE |
—
|
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: IP equals PSPACE | Statement: [PCP theorem, relatedTheorem, IP equals PSPACE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedTheorem Context triple: [PCP theorem, relatedTheorem, IP equals PSPACE]
-
A.
relatedConjecture
Indicates that one conjecture is connected or associated with another conjecture, such as by similarity, dependency, or thematic relation.
-
B.
hasTheorem
Indicates that one entity (typically a mathematical theory, field, or work) includes, establishes, or is associated with a particular theorem.
-
C.
associatedConjecture
Indicates that one entity is linked or connected to a particular conjecture, typically as its subject, source, or relevant context.
-
D.
relatedByFormula
Indicates that one entity is mathematically or logically derived from, or connected to, another according to a specific formula.
-
E.
relatedTest
Indicates that there exists some form of connection or association between one test and another.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc4dd6d48190a5a3f4b86c82b86c |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:19 p.m.