Triple
T9919554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Napanoch, New York |
E185954
|
entity |
| Predicate | distanceToNewYorkCityInMilesApprox |
P2383
|
FINISHED |
| Object | 90 |
—
|
LITERAL 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: 90 | Statement: [Napanoch, New York, distanceToNewYorkCityInMilesApprox, 90]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNewYorkCityInMilesApprox Context triple: [Napanoch, New York, distanceToNewYorkCityInMilesApprox, 90]
-
A.
distanceToNewYorkCity
chosen
Indicates the spatial distance between a given entity’s location and New York City.
-
B.
distanceToNewYorkCityApproxKm
Indicates the approximate physical distance, measured in kilometers, between a given entity’s location and New York City.
-
C.
approximateGreatCircleDistanceMiles
Indicates the approximate distance, measured in miles, between two locations along the great-circle path on the surface of a sphere (typically the Earth).
-
D.
distance to Midtown Manhattan (miles)
Indicates the physical separation between a location and Midtown Manhattan, measured in miles.
-
E.
distanceToAlbanyNewYork
Indicates the spatial distance between a given location and Albany, New York.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb5699bc48190961e036d1131fef0 |
completed | April 2, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:42 p.m.