Triple
T31080115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maildir |
E792074
|
entity |
| Predicate | messageFlagsExample |
P163167
|
FINISHED |
| Object | 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: Seen | Statement: [Maildir, messageFlagsExample, Seen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messageFlagsExample Context triple: [Maildir, messageFlagsExample, Seen]
-
A.
usesFlagsAndBanners
Indicates that an entity employs flags and banners as tools or symbols in its activities, operations, or representations.
-
B.
marksStatus
Indicates that one entity assigns, records, or updates the status or condition of another entity.
-
C.
isFlagsEnum
chosen
Indicates that an enumeration type is intended to be used as a bit field, where its values can be combined using bitwise operations to represent multiple flags simultaneously.
-
D.
flagStatus
Indicates the current state or condition assigned to a flag, such as whether it is active, raised, set, or marked in a particular way.
-
E.
messageSpace
Indicates a relationship where one entity provides or occupies a space or channel through which messages can be sent, stored, or exchanged between parties.
- 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.