Triple
T20836485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NP-hardness |
E512971
|
entity |
| Predicate | complexityStatus |
P142021
|
FINISHED |
| Object | captures worst-case difficulty relative to NP |
—
|
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: captures worst-case difficulty relative to NP | Statement: [NP-hardness, complexityStatus, captures worst-case difficulty relative to NP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complexityStatus Context triple: [NP-hardness, complexityStatus, captures worst-case difficulty relative to NP]
-
A.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
B.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
C.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
implementationStatus
Indicates the current state or progress of carrying out or realizing something, such as a plan, design, or requirement.
-
E.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c326daec8190bd4caa41a4b38833 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:42 p.m.