Triple
T36904844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 676 in New Jersey |
E912741
|
entity |
| Predicate | bridgeApproachFor |
P30350
|
FINISHED |
| Object | Benjamin Franklin Bridge |
—
|
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: Benjamin Franklin Bridge | Statement: [Interstate 676 in New Jersey, bridgeApproachFor, Benjamin Franklin Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeApproachFor Context triple: [Interstate 676 in New Jersey, bridgeApproachFor, Benjamin Franklin Bridge]
-
A.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
B.
bridgeAccessVia
Indicates that access to one entity is provided or routed through another entity acting as a bridge or intermediary.
-
C.
bridgeFeature
Indicates that one entity functions as a structural or functional feature of a bridge associated with another entity.
-
D.
bridgeUsed
chosen
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
E.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fda91e5c8190a06aeccc56992144 |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.