Triple
T30698332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware River bridge system |
E781538
|
entity |
| Predicate | river-crossing network |
P47919
|
FINISHED |
| Object | Delaware River |
—
|
NE NERFINISHED |
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: Delaware River | Statement: [Delaware River bridge system, river-crossing network, Delaware River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: river-crossing network Context triple: [Delaware River bridge system, river-crossing network, Delaware River]
-
A.
riverCrossingConnection
Indicates a connection between two locations that are linked by a route or structure specifically used to cross a river.
-
B.
crossRiverLink
Indicates a connection or route that enables passage across a river between two locations.
-
C.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
D.
riverCrossingStructure
chosen
Indicates a structure that allows passage across a river, such as by spanning or traversing it.
-
E.
waterwayTypeCrossed
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 29, 2026, 8:34 p.m.