Triple
T31080085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maildir |
E792074
|
entity |
| Predicate | storesEachMessageAs |
P30258
|
FINISHED |
| Object | separate file |
—
|
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: separate file | Statement: [Maildir, storesEachMessageAs, separate file]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesEachMessageAs Context triple: [Maildir, storesEachMessageAs, separate file]
-
A.
storesMessagesWhen
Indicates that one entity temporarily holds or buffers messages during the time or condition specified by another entity.
-
B.
storesObjectsAs
chosen
Indicates that one entity keeps or maintains other entities within it as stored items or contents.
-
C.
storedBy
Indicates that one entity is kept, maintained, or held in storage by another entity.
-
D.
storesTracesIn
Indicates that one entity records or preserves trace information within another entity as its storage location.
-
E.
receivesMessageDescribedAs
Indicates that one entity receives a message that is characterized or described in a particular way.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695bd88d88190a7bb4fcded6a5b62 |
completed | May 3, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.