Triple
T19583886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobile, Newfoundland and Labrador |
E490060
|
entity |
| Predicate | locatedInAtlanticCanada |
P136351
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mobile, Newfoundland and Labrador, locatedInAtlanticCanada, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInAtlanticCanada Context triple: [Mobile, Newfoundland and Labrador, locatedInAtlanticCanada, true]
-
A.
regionCanada
Indicates that an entity is located in, associated with, or pertains to the geographic region of Canada.
-
B.
usedInCanadianProvince
Indicates that something is utilized, applied, or in operation within the jurisdiction of a Canadian province.
-
C.
includesCanadianTerritoryPartially
Indicates that one entity geographically encompasses part, but not all, of the territory of Canada.
-
D.
regionCanadianSide
Indicates that the specified region is located on the Canadian side of a border or boundary.
-
E.
locatedInInuitRegion
Indicates that one entity is geographically situated within a region traditionally recognized as part of Inuit territory.
- F. None of above. chosen
Provenance (4 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6404f34b081908aeb9cc9a5ddf539 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:42 p.m.