Triple
T28583779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | progman.exe |
E723439
|
entity |
| Predicate | canBeRunOn |
P11903
|
FINISHED |
| Object | Windows 3.x |
—
|
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.x | Statement: [progman.exe, canBeRunOn, Windows 3.x]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeRunOn Context triple: [progman.exe, canBeRunOn, Windows 3.x]
-
A.
canRunOn
chosen
Indicates that one entity is capable of operating, executing, or functioning on another entity (such as a platform, system, or environment).
-
B.
runsOnHardware
Indicates that a system, software, or process operates using or is executed on a specified hardware platform.
-
C.
canBeRunBehind
Indicates that one entity is capable of being executed or operated in a secondary or background position relative to another entity.
-
D.
canBeDeployedUnder
Indicates that one entity is permitted or suitable to be deployed or operated under the conditions, context, or authority defined by another entity.
-
E.
canBeImplementedWith
Indicates that one entity is capable of being realized, executed, or fulfilled through the use or application of 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_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 28, 2026, 4:16 a.m.