Triple
T6710065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamaica Avenue |
E153114
|
entity |
| Predicate | hasNeighborhood |
P40
|
FINISHED |
| Object | Woodhaven |
E164414
|
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: Woodhaven | Statement: [Jamaica Avenue, hasNeighborhood, Woodhaven]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Woodhaven Context triple: [Jamaica Avenue, hasNeighborhood, Woodhaven]
-
A.
Woodhaven
chosen
Woodhaven is a residential neighborhood in the borough of Queens, New York City, known for its diverse community and proximity to major transit lines and Forest Park.
-
B.
Edgewater
Edgewater is a lakefront community area on Chicago’s North Side known for its dense urban neighborhoods, historic architecture, and proximity to Lake Michigan.
-
C.
Edgewater
Edgewater is a waterfront neighborhood in Miami known for its high-rise residential buildings and proximity to both Biscayne Bay and the city’s urban core.
-
D.
Edgewater
Edgewater is a small coastal city in east-central Florida known for its location along the Indian River in Volusia County.
-
E.
Welhaven
Welhaven is a Norwegian surname most notably associated with the 19th-century poet and critic Johan Sebastian Welhaven.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d105b49c8190932246a727e2c513 |
completed | March 27, 2026, 6:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c751088fc08190abc2eacfb95867f3 |
completed | March 28, 2026, 3:54 a.m. |
Created at: March 27, 2026, 2:06 p.m.