Triple
T32949413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calais, Maine |
E842900
|
entity |
| Predicate | sharesInternationalBoundaryAlong |
P137050
|
FINISHED |
| Object | St. Croix River |
—
|
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: St. Croix River | Statement: [Calais, Maine, sharesInternationalBoundaryAlong, St. Croix River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesInternationalBoundaryAlong Context triple: [Calais, Maine, sharesInternationalBoundaryAlong, St. Croix River]
-
A.
bordersInternationalBoundary
chosen
Indicates that one entity shares an international boundary line directly with another sovereign entity.
-
B.
countyBorder
Indicates that two counties share a common boundary or border with each other.
-
C.
countryBorderFunction
Indicates that one country shares a land or maritime boundary with another country.
-
D.
nationalBorder
Indicates that two geographic or political entities share a common national boundary separating their territories.
-
E.
isPoliticalBoundary
Indicates that one entity serves as a dividing line or border that separates distinct political or administrative jurisdictions.
- 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: May 1, 2026, 1:21 a.m.