Triple
T9312017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | qmail |
E224027
|
entity |
| Predicate | mailQueueDirectory |
P30801
|
FINISHED |
| Object | /var/qmail/queue |
—
|
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: /var/qmail/queue | Statement: [qmail, mailQueueDirectory, /var/qmail/queue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mailQueueDirectory Context triple: [qmail, mailQueueDirectory, /var/qmail/queue]
-
A.
mailedTo
Indicates that something was sent or delivered by mail from one entity to another as the recipient.
-
B.
mailboxModel
Indicates a relationship where an entity functions as or is associated with a specific mailbox configuration or structural model.
-
C.
cacheDirectory
Indicates the directory location where cached data or temporary files are stored for faster subsequent access.
-
D.
smtpCommandKeyword
Indicates that a given token or string functions as a recognized SMTP protocol command keyword in an email transmission session.
-
E.
usesDirectory
chosen
Indicates that one entity makes use of or operates within a particular directory in a file system or organizational structure.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ae96e481909a1af9ea1c91f2b2 |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.