Triple
T32775225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quebec–New York border |
E838181
|
entity |
| Predicate | nearCityInNewYork |
P175510
|
FINISHED |
| Object | Plattsburgh |
—
|
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: Plattsburgh | Statement: [Quebec–New York border, nearCityInNewYork, Plattsburgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearCityInNewYork Context triple: [Quebec–New York border, nearCityInNewYork, Plattsburgh]
-
A.
nearCityOnNewYorkSide
chosen
Indicates that one entity is located near a city that lies on the New York side of a boundary or region.
-
B.
locatedInDirectionFromNYC
Indicates that one place is situated in a specified compass direction relative to New York City.
-
C.
nearestCityTo
Indicates that one city is the closest in distance to a given location or entity compared to all other cities.
-
D.
hasNearbyBorough
Indicates that one borough is geographically close to or adjacent to another borough.
-
E.
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.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:13 a.m.