Triple
T11719300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Canadian English |
E278583
|
entity |
| Predicate | typicalSpeakerRegion |
P29609
|
FINISHED |
| Object | Atlantic provinces of Canada |
—
|
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: Atlantic provinces of Canada | Statement: [Atlantic Canadian English, typicalSpeakerRegion, Atlantic provinces of Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSpeakerRegion Context triple: [Atlantic Canadian English, typicalSpeakerRegion, Atlantic provinces of Canada]
-
A.
countryWithSpeakers
Indicates that a given country is one in which speakers of a specified language (or languages) are present.
-
B.
homeCountryRegion
Indicates the country or broader geographic region that is considered the primary home or origin of an entity.
-
C.
countryRegion
Indicates that a country is located within, or belongs to, a specific geographic or administrative region.
-
D.
typicalHostRegion
Indicates the geographic region where a host is most commonly or characteristically found or associated.
-
E.
regionOfMajorLanguage
chosen
Indicates the geographic region where a particular language is predominantly spoken or holds major usage.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c26e4c8190ae30d906b4fd4221 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.