Triple
T28583788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | progman.exe |
E723439
|
entity |
| Predicate | uiMetaphor |
P82532
|
FINISHED |
| Object | program groups and icons |
—
|
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: program groups and icons | Statement: [progman.exe, uiMetaphor, program groups and icons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uiMetaphor Context triple: [progman.exe, uiMetaphor, program groups and icons]
-
A.
visualMetaphor
chosen
Indicates a relationship where one entity conceptually represents or explains another through a visual analogy or symbolic imagery.
-
B.
userInterface
Indicates a relationship where one entity serves as the interface or interaction layer through which a user engages with another system, service, or resource.
-
C.
userInterfaceSimilarTo
Indicates that one user interface resembles or closely matches another in appearance, layout, or interaction style.
-
D.
visualCompanion
Indicates that one entity serves as a visual counterpart, partner, or accompanying element to another in a visual context.
-
E.
visualElements
Indicates that one entity contains, uses, or is characterized by specific visual components or graphical features associated with 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650ce24ec8190aa08f8477fa41ce0 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:16 a.m.