Triple
T6074622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belle Ewart |
E135368
|
entity |
| Predicate | hasPostalProvince |
P21657
|
FINISHED |
| Object | ON |
—
|
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: ON | Statement: [Belle Ewart, hasPostalProvince, ON]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalProvince Context triple: [Belle Ewart, hasPostalProvince, ON]
-
A.
hasPostalAbbreviationProvince
chosen
Indicates that a province is associated with a specific standardized postal abbreviation used in mailing addresses.
-
B.
hasPostalTerritory
Indicates that one entity possesses or is assigned a specific postal territory within a postal or mailing system.
-
C.
hasProvinceName
Indicates that an entity (such as a province or region) bears or is associated with a specific province name.
-
D.
postalCounty
Indicates the county associated with an entity for postal addressing or mail delivery purposes.
-
E.
hasMajorProvince
Indicates that an entity possesses or is associated with a primary or most significant province within a larger territorial or administrative context.
- 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0575d4ed481908eddc88e9b90e22f |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.