Triple
T2777413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weehawken, New Jersey |
E61605
|
entity |
| Predicate | distanceToMidtownManhattan |
P38946
|
FINISHED |
| Object | approximately 1 mile across the Hudson River |
—
|
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: approximately 1 mile across the Hudson River | Statement: [Weehawken, New Jersey, distanceToMidtownManhattan, approximately 1 mile across the Hudson River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMidtownManhattan Context triple: [Weehawken, New Jersey, distanceToMidtownManhattan, approximately 1 mile across the Hudson River]
-
A.
distanceFromGrandCentral
chosen
Indicates the spatial distance between a given entity and Grand Central.
-
B.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
-
C.
distanceToNewYorkCity
Indicates the spatial distance between a given entity’s location and New York City.
-
D.
distanceToPoughkeepsie
Indicates the spatial distance between a given entity and the location of Poughkeepsie.
-
E.
manhattanConnection
Indicates a direct or indirect connection or route between two entities specifically within the Manhattan area or grid.
- 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_69ab4b7e43c48190997b8fc8fb1663ab |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdd00b65c8190a8ea444308c4fa2b |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.