Triple
T34468394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Canadian Parliament |
E884835
|
entity |
| Predicate | sawProvinceJoin |
P25361
|
FINISHED |
| Object | Manitoba |
—
|
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: Manitoba | Statement: [1st Canadian Parliament, sawProvinceJoin, Manitoba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawProvinceJoin Context triple: [1st Canadian Parliament, sawProvinceJoin, Manitoba]
-
A.
joinedAsProvince
chosen
Indicates that an entity became part of a larger political or administrative unit with the status of a province.
-
B.
sharesProvinceWith
Indicates that two entities are located within, or associated with, the same administrative province.
-
C.
connectsProvincesAlong
Indicates a relationship where something serves as a link or route joining multiple provinces along a specified path or alignment.
-
D.
connectsProvinceOrRegion
Indicates that one entity serves to link or provide a connection between a specific province or region and another entity.
-
E.
stationedInProvince
Indicates that an entity is assigned or based in a particular province as its location or area of operation.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7199bd6788190b0eb050636b84168 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2:01 a.m.