Triple
T14675910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motomachi Park |
E344645
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Harbor View Park |
E381281
|
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: Harbor View Park | Statement: [Motomachi Park, near, Harbor View Park]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Harbor View Park Context triple: [Motomachi Park, near, Harbor View Park]
-
A.
Harbor View Park
chosen
Harbor View Park is a scenic public park in Yokohama’s Yamate district known for its panoramic views over the city and harbor.
-
B.
Harbor Park
Harbor Park is a public riverfront park and recreation area along the Connecticut River in Middletown, Connecticut.
-
C.
Harbor Park
Harbor Park is a waterfront baseball stadium in Norfolk, Virginia, best known as the longtime home of the city’s minor league baseball team.
-
D.
Hurley Park
Hurley Park is a public garden and recreational green space located in Salisbury, North Carolina.
-
E.
Henderson Park
Henderson Park is a public green space and local recreational area in the town of Coldstream in the Scottish Borders.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5666e648190b5faa07076f497b8 |
completed | April 14, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff6ec12de8819097cd83530e54f54b |
completed | May 9, 2026, 5:28 p.m. |
Created at: April 10, 2026, 1:27 a.m.