Triple
T26992540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clique problem |
E679893
|
entity |
| Predicate | reductionFrom |
P161754
|
FINISHED |
| Object | 3-SAT |
—
|
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: 3-SAT | Statement: [Clique problem, reductionFrom, 3-SAT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reductionFrom Context triple: [Clique problem, reductionFrom, 3-SAT]
-
A.
reduction
Indicates a relationship where something is decreased in amount, size, intensity, or degree compared to a prior state or reference.
-
B.
reduces
Indicates that one entity causes a decrease in the amount, intensity, degree, or impact of another entity.
-
C.
reducesTo
Indicates that one expression, structure, or state can be transformed or simplified into another, typically more basic or canonical, form.
-
D.
reducedRepresentationOf
Indicates that one entity is a simplified, compressed, or lower-detail version of another entity while preserving its essential information or structure.
-
E.
reductionDate
Indicates the date on which a reduction (such as in amount, level, or status) takes effect or is officially recorded.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621915ee48190b508025afa2fb4fc |
completed | May 2, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 27, 2026, 6:52 a.m.