Triple
T5261979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware River and Bay Authority |
E118845
|
entity |
| Predicate | bridgeTypeManaged |
P1787
|
FINISHED |
| Object | suspension 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: suspension bridge | Statement: [Delaware River and Bay Authority, bridgeTypeManaged, suspension bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeTypeManaged Context triple: [Delaware River and Bay Authority, bridgeTypeManaged, suspension bridge]
-
A.
bridgeType
chosen
Indicates the specific kind or classification of a bridge associated with an entity.
-
B.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
C.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
D.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd0c5f48190a1be89314c59f96b |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.