Triple
T9645589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhattan via Williamsburg Bridge |
E233185
|
entity |
| Predicate | associatedWithBridgeOpeningYear |
P47616
|
FINISHED |
| Object | 1903 |
—
|
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: 1903 | Statement: [Manhattan via Williamsburg Bridge, associatedWithBridgeOpeningYear, 1903]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBridgeOpeningYear Context triple: [Manhattan via Williamsburg Bridge, associatedWithBridgeOpeningYear, 1903]
-
A.
originalBridgeOpened
Indicates that the first or initial version of a bridge was opened for use or put into operation.
-
B.
bridgeOpened
chosen
Indicates that a bridge has transitioned from a closed or inactive state to being open and available for use.
-
C.
railTunnelOpeningYear
Indicates the calendar year in which a rail tunnel was officially opened for use.
-
D.
hasSwingBridge
Indicates that one entity possesses or includes a swing bridge, i.e., a bridge section that can pivot or rotate to allow passage (typically of water traffic).
-
E.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
- 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b7fd2308190803a196ecdc80d76 |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:12 p.m.