Triple
T7666048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NP-completeness |
E173625
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computational complexity theory concept |
C7186
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: computational complexity theory concept Context triple: [NP-completeness, instanceOf, computational complexity theory concept]
-
A.
foundational principle in theoretical computer science
chosen
A foundational principle in theoretical computer science is a core, abstract concept or rule—such as computability, complexity, or formal language theory—that underlies and unifies the study of algorithms, computation models, and their inherent limits.
-
B.
model of computation
A model of computation is an abstract mathematical framework that defines how algorithms are represented and executed, specifying the rules, operations, and resources available for performing computations.
-
C.
complexity measure
A complexity measure is a quantitative function or criterion used to assess and compare the intricacy, difficulty, or resource requirements of objects, systems, or problems.
-
D.
theoretical computer science conference
A theoretical computer science conference is a formal academic gathering where researchers present, discuss, and critique new results and ideas in areas such as algorithms, complexity theory, cryptography, and formal methods.
-
E.
concept in number theory
A concept in number theory is an abstract idea or construct that describes properties, relationships, or structures involving integers and related numerical systems.
- F. None of above.
Provenance (1 batch)
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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4 p.m.