Triple
T14394714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLion |
E356923
|
entity |
| Predicate | supportsKeymap |
P114077
|
FINISHED |
| Object | customizable keymaps |
—
|
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: customizable keymaps | Statement: [CLion, supportsKeymap, customizable keymaps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsKeymap Context triple: [CLion, supportsKeymap, customizable keymaps]
-
A.
supportsKeyboard
Indicates that one entity is compatible with or able to be operated using a keyboard as an input method.
-
B.
keySupportFrom
Indicates that one entity provides essential backing, endorsement, or assistance that is crucial for the success or continuation of another entity or action.
-
C.
supportsKeyboardAndMouse
Indicates that the subject provides compatibility with and can be operated using both a keyboard and a mouse.
-
D.
hasKeyboard
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
-
E.
keyboardFeature
Indicates that one entity is a feature, characteristic, or functional attribute of a keyboard.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de902d114881908a8f3c01b3c6d309 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:16 a.m.