Triple
T3061170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows 32-bit |
E61998
|
entity |
| Predicate | usesExecutableFormat |
P8462
|
FINISHED |
| Object | PE (Portable Executable) 32-bit |
—
|
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: PE (Portable Executable) 32-bit | Statement: [Windows 32-bit, usesExecutableFormat, PE (Portable Executable) 32-bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesExecutableFormat Context triple: [Windows 32-bit, usesExecutableFormat, PE (Portable Executable) 32-bit]
-
A.
hasFileFormat
chosen
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
B.
executableName
Indicates the specific name of a program or binary file that is intended to be executed.
-
C.
isExportable
Indicates that something can be legally and practically transferred or sent out from one jurisdiction, system, or context to another.
-
D.
defaultPackageFormat
Indicates the standard or primary packaging format that is used by default for an item or distribution.
-
E.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e9e1e248190b5ed5ebcdad1321e |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.