Triple
T36049779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doukhobors |
E1042774
|
entity |
| Predicate | majorSettlementCountry |
P41930
|
FINISHED |
| Object | Canada |
—
|
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 | Statement: [Doukhobors, majorSettlementCountry, Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorSettlementCountry Context triple: [Doukhobors, majorSettlementCountry, Canada]
-
A.
notableSettlementCountry
chosen
Indicates that a country is notably associated with a particular settlement, such as being its primary or most recognized national affiliation.
-
B.
typicalSettlementCountry
Indicates the country in which an entity’s financial transactions, obligations, or trades are most commonly settled.
-
C.
mainCountry
Indicates that one country is the primary or most significant country associated with a given entity or context.
-
D.
hasHumanSettlementAlong
Indicates that a human settlement is located adjacent to or distributed along the length of a specified geographic feature or route.
-
E.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:07 p.m.