Triple
T28411406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kemeny–Young method |
E719672
|
entity |
| Predicate | computationalProblem |
P29141
|
FINISHED |
| Object | Kemeny score computation is NP-hard |
—
|
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: Kemeny score computation is NP-hard | Statement: [Kemeny–Young method, computationalProblem, Kemeny score computation is NP-hard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computationalProblem Context triple: [Kemeny–Young method, computationalProblem, Kemeny score computation is NP-hard]
-
A.
computationalClass
chosen
Indicates that two entities share the same computational complexity class or that one entity is categorized within a specified computational complexity class.
-
B.
computationInput
Indicates that an entity serves as input data or parameters consumed by a computation or processing activity.
-
C.
problemType
Indicates the specific category or classification of a problem within a defined problem space or system.
-
D.
computationalCost
Indicates the amount of computing resources (such as time, memory, or processing power) required to perform a given operation or process.
-
E.
problemTypeSolved
Indicates that a given problem has been successfully solved or resolved by a particular entity or method.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 1:27 a.m.