Triple
T11052402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Route 129 |
E261287
|
entity |
| Predicate | crosses |
P416
|
FINISHED |
| Object | Assunpink Creek |
E525305
|
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: Assunpink Creek | Statement: [New Jersey Route 129, crosses, Assunpink Creek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Assunpink Creek Context triple: [New Jersey Route 129, crosses, Assunpink Creek]
-
A.
Assunpink Creek
chosen
Assunpink Creek is a stream in central New Jersey historically notable as the site of a pivotal American Revolutionary War engagement during the Trenton campaign.
-
B.
Neskowin Creek
Neskowin Creek is a small coastal stream in Tillamook County, Oregon, that flows through the community of Neskowin into the Pacific Ocean.
-
C.
Hannibal Creek
Hannibal Creek is a waterway after which the city of Hannibal, Missouri, is named.
-
D.
Overpeck Creek
Overpeck Creek is a tributary stream in northeastern New Jersey that flows through Bergen County into the Hackensack River, bordered by wetlands, parks, and urban communities.
-
E.
Nomini Creek
Nomini Creek is a tidal tributary of the Potomac River in Westmoreland County, Virginia, known for its historical plantation-era surroundings.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7986c0df88190b29d71db5538450a |
completed | April 9, 2026, 12:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec869957481909ea4fded01851b70 |
completed | May 9, 2026, 5:38 a.m. |
Created at: April 8, 2026, 9:26 p.m.