Triple
T21568932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelling Post Office |
E532233
|
entity |
| Predicate | mailExchangeMethod |
P9798
|
FINISHED |
| Object | lineside mail bag apparatus |
—
|
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: lineside mail bag apparatus | Statement: [Travelling Post Office, mailExchangeMethod, lineside mail bag apparatus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mailExchangeMethod Context triple: [Travelling Post Office, mailExchangeMethod, lineside mail bag apparatus]
-
A.
mailRoute
Indicates a route or path along which mail or postal items are transported between locations.
-
B.
mailboxModel
Indicates a relationship where an entity functions as or is associated with a specific mailbox configuration or structural model.
-
C.
exchange
chosen
Indicates a reciprocal transfer of something (such as goods, information, or services) between two or more entities.
-
D.
mailedTo
Indicates that something was sent or delivered by mail from one entity to another as the recipient.
-
E.
mailTypesHandled
Indicates that an entity is capable of processing or dealing with specific types or categories of mail.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cad95c8190ab165ced6f242302 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.