Triple
T28583762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | progman.exe |
E723439
|
entity |
| Predicate | replacedAsDefaultShellBy |
P33704
|
FINISHED |
| Object | explorer.exe |
—
|
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: explorer.exe | Statement: [progman.exe, replacedAsDefaultShellBy, explorer.exe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedAsDefaultShellBy Context triple: [progman.exe, replacedAsDefaultShellBy, explorer.exe]
-
A.
previousDefaultShell
chosen
Indicates that one shell was the default shell for an entity before being replaced by another default shell.
-
B.
replacedOnPlatformBy
Indicates that one entity has been superseded or taken over by another entity on a particular platform.
-
C.
replacedSystemBasedOn
Indicates that one system was substituted for another specifically on the basis of certain criteria, conditions, or evaluations.
-
D.
rebootOf
Indicates that one work is a new version that restarts or reimagines the story, continuity, or franchise of another earlier work.
-
E.
replacedInSystemVersion
Indicates that one entity has been superseded or substituted by another in a specific version of a system.
- 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_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:16 a.m.