Triple
T37883164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMM386.EXE |
E944921
|
entity |
| Predicate | commonConfigLine |
P199902
|
FINISHED |
| Object | DEVICE=EMM386.EXE |
—
|
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: DEVICE=EMM386.EXE | Statement: [EMM386.EXE, commonConfigLine, DEVICE=EMM386.EXE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonConfigLine Context triple: [EMM386.EXE, commonConfigLine, DEVICE=EMM386.EXE]
-
A.
lineConfiguration
Indicates that the entities participate together in a specific arrangement or pattern along a line.
-
B.
systemStartLine
Indicates the line or point in a sequence where a system begins its operation or execution.
-
C.
computerLine
Indicates a relationship where one entity is a line of text, code, or output produced or displayed by a computer.
-
D.
defaultConfigurationTool
Indicates that one tool is designated as the standard or primary utility used for configuring another system or component.
-
E.
mainLine
Indicates that something serves as the primary or central line, route, or sequence among a set of related lines.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69ff632176b0819084610ae2e57ab679 |
completed | May 9, 2026, 4:38 p.m. |
Created at: May 3, 2026, 4:19 p.m.