Triple
T31080118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maildir |
E792074
|
entity |
| Predicate | messageFlagsLocation |
P62335
|
FINISHED |
| Object | stored in filename suffix in cur directory |
—
|
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: stored in filename suffix in cur directory | Statement: [Maildir, messageFlagsLocation, stored in filename suffix in cur directory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messageFlagsLocation Context triple: [Maildir, messageFlagsLocation, stored in filename suffix in cur directory]
-
A.
marksLocationOf
Indicates that one entity serves as a marker, sign, or indicator specifying the location of another entity.
-
B.
locationOfMark
Indicates that one entity is the place or position where a particular mark is found or applied.
-
C.
labelLocation
Indicates that a label or identifier is associated with a specific spatial or geographic location.
-
D.
textLocation
Indicates the spatial or positional relationship of a piece of text within a larger document, page, or layout.
-
E.
metadataLocation
chosen
Indicates the location or source where descriptive or administrative information about an entity is stored or can be accessed.
- 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_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:02 p.m.