Triple
T16171530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell, Majors and Waddell |
E392447
|
entity |
| Predicate | mailServiceType |
P14605
|
FINISHED |
| Object | express mail |
—
|
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: express mail | Statement: [Russell, Majors and Waddell, mailServiceType, express mail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mailServiceType Context triple: [Russell, Majors and Waddell, mailServiceType, express mail]
-
A.
mailedTo
Indicates that something was sent or delivered by mail from one entity to another as the recipient.
-
B.
mailContractWith
Indicates that one party sends or delivers a contract to another party via mail as part of a transactional or formal process.
-
C.
mailboxModel
Indicates a relationship where an entity functions as or is associated with a specific mailbox configuration or structural model.
-
D.
emailSupport
Indicates that one entity provides assistance or help to another via email communication.
-
E.
postalService
chosen
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb7ab1481908fc35bfc8c56e5f2 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.