Triple
T28392773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit, Michigan Territory |
E719198
|
entity |
| Predicate | neighboringPoliticalEntity |
P163736
|
FINISHED |
| Object | Upper Canada |
—
|
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: Upper Canada | Statement: [Detroit, Michigan Territory, neighboringPoliticalEntity, Upper Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringPoliticalEntity Context triple: [Detroit, Michigan Territory, neighboringPoliticalEntity, Upper Canada]
-
A.
geopoliticalNeighbors
chosen
Indicates that two geopolitical entities share a common border or are directly adjacent to each other territorially.
-
B.
geographicallyAdjacentTo
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
-
C.
neighboringCountryBySea
Indicates that one country is adjacent to another with their territories touching via a shared sea boundary rather than solely by land.
-
D.
borderingRepublic
Indicates that one republic shares a land or maritime border with another republic.
-
E.
geographicNeighbors
Indicates that two geographic entities share a common boundary or are directly adjacent to each other in space.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 1:14 a.m.