Triple
T30395204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coburn Gore border station |
E773196
|
entity |
| Predicate | adjacentForeignSettlement |
P137070
|
FINISHED |
| Object | Woburn, Quebec |
—
|
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: Woburn, Quebec | Statement: [Coburn Gore border station, adjacentForeignSettlement, Woburn, Quebec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentForeignSettlement Context triple: [Coburn Gore border station, adjacentForeignSettlement, Woburn, Quebec]
-
A.
hasAdjacentSettlement
Indicates that one settlement is located directly next to or bordering another settlement.
-
B.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
C.
nearestForeignCity
Indicates that one city is the geographically closest city located in a different country relative to another city.
-
D.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
-
E.
terminusNearbySettlement
chosen
Indicates that a transportation terminus (such as a station or terminal) is located close to a particular settlement.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 8:02 p.m.