Triple
T8574257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MS-DOS Executive |
E203006
|
entity |
| Predicate | fileDisplayMode |
P30377
|
FINISHED |
| Object | single directory listing |
—
|
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: single directory listing | Statement: [MS-DOS Executive, fileDisplayMode, single directory listing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileDisplayMode Context triple: [MS-DOS Executive, fileDisplayMode, single directory listing]
-
A.
displayMode
chosen
Indicates how content or information is visually presented or arranged to the user.
-
B.
displayType
Indicates the manner or format in which something is presented, shown, or rendered.
-
C.
dataTypeDisplayed
Indicates that a particular data type is currently being shown or rendered in a given context or interface.
-
D.
displayState
Indicates the current visual or presentation status of an item, such as whether and how it is shown, hidden, or rendered in a user interface or display context.
-
E.
displayConfiguration
Indicates a relationship where one entity defines or presents the arrangement, layout, or settings used to visually display 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea947f188190af469babaa73ddf6 |
completed | March 31, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:21 p.m.