Triple
T31799110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Fairfield–Andover border crossing |
E811678
|
entity |
| Predicate | borderSideSettlementUS |
P46520
|
FINISHED |
| Object | Fort Fairfield, Maine |
—
|
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: Fort Fairfield, Maine | Statement: [Fort Fairfield–Andover border crossing, borderSideSettlementUS, Fort Fairfield, Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderSideSettlementUS Context triple: [Fort Fairfield–Andover border crossing, borderSideSettlementUS, Fort Fairfield, Maine]
-
A.
borderStateOnUSSide
Indicates that a state is located on the U.S. side of an international border shared with another country.
-
B.
borderSettlement
chosen
Indicates that a settlement is located near or along a political or administrative border.
-
C.
borderCityOnUSSide
Indicates that a city is located on the U.S. side of an international border shared with another country.
-
D.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
E.
borderDirectionFromUS
Indicates the compass direction in which a country or region lies relative to the United States along their shared border.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: April 30, 2026, 11:41 p.m.