Triple
T24528568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amherst, Nova Scotia |
E606734
|
entity |
| Predicate | nearestProvincialCapital |
P64444
|
FINISHED |
| Object | Halifax, Nova Scotia |
—
|
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: Halifax, Nova Scotia | Statement: [Amherst, Nova Scotia, nearestProvincialCapital, Halifax, Nova Scotia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestProvincialCapital Context triple: [Amherst, Nova Scotia, nearestProvincialCapital, Halifax, Nova Scotia]
-
A.
capitalOfProvinceNearby
chosen
Indicates that a city serves as the capital of a province that is geographically close to a specified reference location or area.
-
B.
nearbyTraditionalCapital
Indicates that one location is geographically close to a place that serves or served as a traditional capital.
-
C.
countyCapitalNearby
Indicates that a county’s capital city is located close to a specified place or entity.
-
D.
regionCapitalNearby
Indicates that a capital city of a region is located close to the referenced place or entity.
-
E.
countryCapitalNearby
Indicates that a country’s capital city is geographically close to a specified location or entity.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.