Triple
T30319823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wabun Lake Station Post Office Station |
E771166
|
entity |
| Predicate | countryPostalOperator |
P14605
|
FINISHED |
| Object | Canada Post |
—
|
NE NERFINISHED |
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: [Wabun Lake Station Post Office Station, countryPostalOperator, Canada Post]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryPostalOperator Context triple: [Wabun Lake Station Post Office Station, countryPostalOperator, Canada Post]
-
A.
governingPostalOperator
Indicates that one postal operator has official authority or regulatory control over the operations of another postal service or postal area.
-
B.
postalService
chosen
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
C.
sharePostalSystemElements
Indicates that two entities use or have in common specific components or features of the same postal system.
-
D.
postalSystemType
Indicates the type or classification of a postal system associated with an entity.
-
E.
hasPostalSystemOf
Indicates that one entity possesses, uses, or is characterized by the postal system belonging to 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: April 29, 2026, 7:52 p.m.