Triple
T21371134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rindge, New Hampshire |
E527063
|
entity |
| Predicate | borderingTown |
P224
|
FINISHED |
| Object | Jaffrey, New Hampshire |
E208666
|
NE FINISHED |
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: Jaffrey, New Hampshire | Statement: [Rindge, New Hampshire, borderingTown, Jaffrey, New Hampshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingTown Context triple: [Rindge, New Hampshire, borderingTown, Jaffrey, New Hampshire]
-
A.
oppositeTownAcrossBorder
Indicates that one town is located directly across a border from another town, positioned as its opposite counterpart.
-
B.
borderTownAcrossBorder
Indicates that a town lies on one side of a border directly opposite or adjacent to a town on the other side of that border.
-
C.
borderedBy
chosen
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
E.
cityIsBorderCity
Indicates that a city is located on or near a boundary between two regions, countries, or administrative areas.
- F. None of above.
Provenance (4 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0ae92c88190a3d3097f5b268a79 |
completed | April 22, 2026, 11:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0f96184a28819091a1a3930107cc24 |
completed | May 21, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:10 p.m.