Triple
T28583756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | progman.exe |
E723439
|
entity |
| Predicate | usedAsDefaultShellIn |
P183111
|
FINISHED |
| Object | Windows 3.0 |
—
|
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: Windows 3.0 | Statement: [progman.exe, usedAsDefaultShellIn, Windows 3.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsDefaultShellIn Context triple: [progman.exe, usedAsDefaultShellIn, Windows 3.0]
-
A.
previousDefaultShell
Indicates that one shell was the default shell for an entity before being replaced by another default shell.
-
B.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
C.
usedTerminal
Indicates that an entity made use of or interacted with a particular terminal or endpoint device.
-
D.
novaShellDetected
Indicates that an expanding shell of material produced by a nova event has been observed or identified.
-
E.
hasShell
Indicates that an entity possesses or is covered by a shell as a physical protective structure.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: April 28, 2026, 4:16 a.m.