Triple
T32893388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Hope–Lambertville Bridge |
E841398
|
entity |
| Predicate | riverBankOnWest |
P180178
|
FINISHED |
| Object | Pennsylvania bank of Delaware 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: Pennsylvania bank of Delaware River | Statement: [New Hope–Lambertville Bridge, riverBankOnWest, Pennsylvania bank of Delaware River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverBankOnWest Context triple: [New Hope–Lambertville Bridge, riverBankOnWest, Pennsylvania bank of Delaware River]
-
A.
riverBankOnEastSide
Indicates that a river bank is located on the eastern side of a river or watercourse.
-
B.
riverBankOnSouthSide
Indicates that a river bank is located on the southern side of a specified river or watercourse.
-
C.
riverBankTwo
Indicates a relationship where something is located on or associated with the second of two identified banks of a river.
-
D.
riverBankOnOneSide
Indicates that a river flows adjacent to and borders only one side of a specified bank or land area.
-
E.
riverBankOnUSSide
Indicates that the river bank being referred to is located on the United States side of the river.
- F. None of above. chosen
Provenance (4 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: May 1, 2026, 1:18 a.m.