Triple
T26992554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clique problem |
E679893
|
entity |
| Predicate | isHardFor |
P142792
|
FINISHED |
| Object | NP |
—
|
NE NERFINISHED |
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 | Statement: [Clique problem, isHardFor, NP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHardFor Context triple: [Clique problem, isHardFor, NP]
-
A.
impliesHardness
chosen
Indicates that one entity suggests, entails, or leads to the conclusion that another entity possesses hardness.
-
B.
hardness
Indicates the degree to which one entity resists being scratched, indented, or deformed by another.
-
C.
showsHardnessOf
Indicates that something displays or reveals the degree of hardness possessed by another entity.
-
D.
hasDifficultyWith
Indicates that one entity experiences problems, challenges, or lack of proficiency in dealing with, understanding, or performing something related to another entity.
-
E.
isEasierThan
Indicates that one entity requires less effort, difficulty, or complexity to accomplish, understand, or deal with than another entity.
- 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_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. |
Created at: April 27, 2026, 6:52 a.m.