Triple
T31080099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maildir |
E792074
|
entity |
| Predicate | messageFileNaming |
P2555
|
FINISHED |
| Object | unique filenames |
—
|
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: unique filenames | Statement: [Maildir, messageFileNaming, unique filenames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messageFileNaming Context triple: [Maildir, messageFileNaming, unique filenames]
-
A.
fileName
Indicates the name assigned to a file, typically used to identify or reference that file within a system or context.
-
B.
documentationName
Indicates the name or title assigned to a specific piece of documentation.
-
C.
namingStructure
chosen
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
D.
filenameType
Indicates the type or category associated with a given filename (e.g., file format, role, or classification).
-
E.
maximumFileNameLength
Indicates the maximum number of characters allowed in a file name within a given system or context.
- 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.