Triple
T21088302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karp reduction |
E519560
|
entity |
| Predicate | canonicalExampleTo |
P135707
|
FINISHED |
| Object | CLIQUE |
—
|
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: CLIQUE | Statement: [Karp reduction, canonicalExampleTo, CLIQUE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalExampleTo Context triple: [Karp reduction, canonicalExampleTo, CLIQUE]
-
A.
isCanonicalExampleOf
chosen
Indicates that something serves as a standard or typical instance that exemplifies a concept, category, or pattern.
-
B.
centralExample
Indicates that one entity serves as the primary or most representative example of another entity or concept.
-
C.
standardExample
Indicates that something is a typical or canonical instance used to illustrate a general case or concept.
-
D.
baseExamples
Indicates that something serves as a fundamental or illustrative example for understanding or demonstrating another concept, item, or case.
-
E.
usedAsExampleIn
Indicates that one entity is cited or presented as an illustrative example within another entity, such as a text, discussion, or explanation.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094cebe08190bb10f51a45c244ec |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:50 p.m.