Triple
T8883232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 280 (New Jersey) |
E211460
|
entity |
| Predicate | bridgeTypeAtPassaicRiver |
P1787
|
FINISHED |
| Object | steel through arch bridge |
—
|
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: steel through arch bridge | Statement: [Interstate 280 (New Jersey), bridgeTypeAtPassaicRiver, steel through arch bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeTypeAtPassaicRiver Context triple: [Interstate 280 (New Jersey), bridgeTypeAtPassaicRiver, steel through arch bridge]
-
A.
bridgeType
chosen
Indicates the specific kind or classification of a bridge associated with an entity.
-
B.
bayonneBridgeCarries
Indicates that the Bayonne Bridge serves as a route or conduit for carrying or transporting something (such as vehicles, traffic, or infrastructure) across its span.
-
C.
hasPassengerBridge
Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
-
D.
riverCrossingStructure
Indicates a structure that allows passage across a river, such as by spanning or traversing it.
-
E.
bayonneBridgeOpened
Indicates that the Bayonne Bridge has been officially opened for use or traffic.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc616b2d988190b923ef1e33aab787 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.