Triple
T9739085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware Aqueduct |
E236139
|
entity |
| Predicate | bypassTunnelLocation |
P90434
|
FINISHED |
| Object | under Hudson River between Newburgh and Wappinger |
—
|
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: under Hudson River between Newburgh and Wappinger | Statement: [Delaware Aqueduct, bypassTunnelLocation, under Hudson River between Newburgh and Wappinger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bypassTunnelLocation Context triple: [Delaware Aqueduct, bypassTunnelLocation, under Hudson River between Newburgh and Wappinger]
-
A.
bypassedLocation
Indicates that an entity intentionally passed by or went around a specific location without stopping or entering it.
-
B.
usesTunnel
Indicates that one entity makes use of a tunnel as a passage or route to reach or connect to another entity.
-
C.
bypassType
Indicates the specific kind or method of bypass used to circumvent or route around a normal process, path, or control.
-
D.
hasBypass
Indicates that one entity includes or is equipped with an alternative route or mechanism that circumvents or avoids another entity or process.
-
E.
bypassOpenedIn
Indicates that a bypass route or channel was opened or became available within a specified location or context.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef43fec8190987628f401a27436 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:22 p.m.