Triple
T21763232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max-SAT |
E537213
|
entity |
| Predicate | decisionVersionComplexity |
P28756
|
FINISHED |
| Object | NP-complete |
—
|
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: NP-complete | Statement: [Max-SAT, decisionVersionComplexity, NP-complete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionVersionComplexity Context triple: [Max-SAT, decisionVersionComplexity, NP-complete]
-
A.
hasReasoningComplexity
Indicates that an action, process, or decision involves a certain level or type of cognitive or logical complexity in its reasoning.
-
B.
hasComplexity
chosen
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
C.
complexityStatus
Indicates the current level or state of complexity associated with an entity or process.
-
D.
complexVersionConclusion
Indicates that something serves as a final, possibly multi-faceted or detailed outcome or resolution of a more intricate or compound version of something else.
-
E.
decisionMakingLevel
Indicates the degree or hierarchy of authority an entity has in making decisions within a given context.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031a711dc8190a786c9849dc344e8 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.