Triple
T38476256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malécites |
E915556
|
entity |
| Predicate | primaryProvinceInCanada |
P152583
|
FINISHED |
| Object | New Brunswick |
E122688
|
NE 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: New Brunswick | Statement: [Malécites, primaryProvinceInCanada, New Brunswick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryProvinceInCanada Context triple: [Malécites, primaryProvinceInCanada, New Brunswick]
-
A.
inCanadianProvince
chosen
Indicates that one entity is located within, or is a part of, a specified Canadian province.
-
B.
currentProvinceOfTerritory
Indicates that a given province is the one that currently has administrative authority over a specified territory.
-
C.
exportProvince
Indicates the province from which goods, services, or resources are exported.
-
D.
traditionalProvince
Indicates that an entity is located in, associated with, or belongs to a historically recognized or customary provincial region rather than a modern administrative unit.
-
E.
separatesCanadianProvince
Indicates that one entity serves as a dividing boundary between a specified Canadian province and another geographic area.
- F. None of above.
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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ea7f45848190a62c3eede9933260 |
completed | June 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.