Triple
T7858020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outlook Express |
E182424
|
entity |
| Predicate | storesMessagesIn |
P63988
|
FINISHED |
| Object | DBX files |
—
|
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: DBX files | Statement: [Outlook Express, storesMessagesIn, DBX files]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesMessagesIn Context triple: [Outlook Express, storesMessagesIn, DBX files]
-
A.
store
chosen
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
-
B.
storesIndexesIn
Indicates that one entity maintains and holds index data within another storage entity or system.
-
C.
storesConfigurationFor
Indicates that one entity holds or maintains configuration settings that are used by or apply to another entity.
-
D.
storesMetadataIn
Indicates that one entity holds or maintains descriptive or configuration metadata about another entity within a specified storage location or system.
-
E.
storesKeys
Indicates that one entity holds or retains the keys belonging to or used by 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb1a76f8648190976b488d0d8658ef |
completed | March 31, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:52 p.m.