Triple
T30286285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bournemouth Mail Centre |
E770244
|
entity |
| Predicate | handlesMailType |
P124225
|
FINISHED |
| Object | letters |
—
|
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: letters | Statement: [Bournemouth Mail Centre, handlesMailType, letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesMailType Context triple: [Bournemouth Mail Centre, handlesMailType, letters]
-
A.
mailTypesHandled
chosen
Indicates that an entity is capable of processing or dealing with specific types or categories of mail.
-
B.
mailSystemType
Indicates the type or category of mail system associated with or used by an entity.
-
C.
hasTypeOfRecipient
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
-
D.
handlesOperationType
Indicates that an entity is responsible for processing or managing a specific type or category of operation.
-
E.
handlesFrom
Indicates that one entity is responsible for managing, processing, or dealing with something originating from another entity.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 7:46 p.m.