Triple
T31080128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maildir |
E792074
|
entity |
| Predicate | typicalBaseDirectory |
P60205
|
FINISHED |
| Object | ~/Maildir |
—
|
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: ~/Maildir | Statement: [Maildir, typicalBaseDirectory, ~/Maildir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBaseDirectory Context triple: [Maildir, typicalBaseDirectory, ~/Maildir]
-
A.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
B.
baseLocation
chosen
Indicates the primary place where an entity is based, headquartered, or operates from as its main location.
-
C.
typicalConfigFile
Indicates that something is a standard or commonly used configuration file associated with a given entity or system.
-
D.
typicalEntryFile
Indicates that a given file is the standard or primary entry point typically used to start or access something (such as a program, project, or package).
-
E.
typicalBaseClass
Indicates that one class is the usual or standard superclass (base class) from which another class is typically derived.
- 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_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:02 p.m.