Triple
T37382083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worthington, Massachusetts |
E928456
|
entity |
| Predicate | nearestSmallCity |
P188940
|
FINISHED |
| Object | Northampton, Massachusetts |
—
|
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: Northampton, Massachusetts | Statement: [Worthington, Massachusetts, nearestSmallCity, Northampton, Massachusetts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestSmallCity Context triple: [Worthington, Massachusetts, nearestSmallCity, Northampton, Massachusetts]
-
A.
nearestCityTo
Indicates that one city is the closest in distance to a given location or entity compared to all other cities.
-
B.
largestNearbyCity
Indicates that one city is the largest (by population, area, or another defined metric) among the cities located within a specified nearby region of another place or city.
-
C.
nearestInlandCity
Indicates that one city is the closest inland (non-coastal) city to another specified location.
-
D.
nearestCitySouth
Indicates that one city is the closest city located to the south of another city.
-
E.
countyCapitalNearby
Indicates that a county’s capital city is located close to a specified place or entity.
- F. None of above. chosen
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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 3, 2026, 4:16 p.m.