Triple
T1881477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3501 |
E39860
|
entity |
| Predicate | definesMailboxNameSyntax |
P2555
|
FINISHED |
| Object | hierarchical mailbox names |
—
|
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: hierarchical mailbox names | Statement: [RFC 3501, definesMailboxNameSyntax, hierarchical mailbox names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesMailboxNameSyntax Context triple: [RFC 3501, definesMailboxNameSyntax, hierarchical mailbox names]
-
A.
namedSpace
Indicates that an entity has been assigned or is associated with a specific name within a particular namespace or naming context.
-
B.
postalServiceDesignation
Indicates the official classification or label assigned to an entity by a postal service for mail handling, routing, or addressing purposes.
-
C.
namingStructure
chosen
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
D.
addressPrefix
Indicates that one address string serves as the starting portion or leading segment of another address.
-
E.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb4f53f408190ae30e1a12721e7d7 |
completed | March 7, 2026, 5:17 a.m. |
| PD | Predicate disambiguation | batch_69abafe497a88190a1da6af2888b71b4 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.