Triple
T26992548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clique problem |
E679893
|
entity |
| Predicate | searchVariant |
P37453
|
FINISHED |
| Object | find a clique of size at least k |
—
|
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: find a clique of size at least k | Statement: [Clique problem, searchVariant, find a clique of size at least k]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchVariant Context triple: [Clique problem, searchVariant, find a clique of size at least k]
-
A.
searchesVia
Indicates that an entity performs a search by means of, or using, a specified tool, method, or channel.
-
B.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
C.
searchFeature
Indicates that an entity provides or supports functionality for searching or querying information or items.
-
D.
typeOfSearch
chosen
Indicates the specific kind or category of search operation being performed or requested between entities.
-
E.
soughtFor
Indicates that one entity is being searched for, pursued, or wanted by another, often for a specific purpose or reason.
- 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_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 6:52 a.m.