Triple
T3806167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NT |
E93011
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object | Canada Post |
E209822
|
NE 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: Canada Post | Statement: [NT, usedBy, Canada Post]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Canada Post Context triple: [NT, usedBy, Canada Post]
-
A.
Canada Post
chosen
Canada Post is the primary postal operator in Canada, providing mail and parcel delivery services nationwide.
-
B.
Australia Post
Australia Post is the government-owned corporation responsible for providing postal and related services across Australia.
-
C.
United States Postal Service
The United States Postal Service is an independent agency of the U.S. federal government responsible for providing nationwide postal delivery and related mail services.
-
D.
Swiss Post
Swiss Post is Switzerland’s national postal service provider, responsible for mail delivery, logistics, and various financial and digital services across the country.
-
E.
Royal Mail
Royal Mail is the United Kingdom’s long-established national postal service and courier company responsible for mail collection and delivery across the country and internationally.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aee809c5c481909d5412cdd33b458d |
completed | March 9, 2026, 3:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4fb2d7be48190a041e59b706751a4 |
completed | March 14, 2026, 6:07 a.m. |
Created at: March 9, 2026, 3:16 p.m.