Triple
T31080091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maildir |
E792074
|
entity |
| Predicate | purposeOfCurDirectory |
P127928
|
FINISHED |
| Object | holding messages that have been seen |
—
|
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: holding messages that have been seen | Statement: [Maildir, purposeOfCurDirectory, holding messages that have been seen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfCurDirectory Context triple: [Maildir, purposeOfCurDirectory, holding messages that have been seen]
-
A.
scriptPurpose
Indicates the intended function or role that a script is designed to perform.
-
B.
dimensionOfCurrent
Indicates the dimensional property (such as magnitude or units) associated with the current in a given context.
-
C.
sectionPurpose
chosen
Indicates that a section exists for the purpose of fulfilling or serving a specified function, role, or intended use.
-
D.
findsPurposeThrough
Indicates that one entity derives its sense of purpose, meaning, or fulfillment through its relationship with or actions involving another entity.
-
E.
curvePurpose
Indicates that a curve exists or is defined for a particular purpose, function, or intended use.
- 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_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:02 p.m.