Triple
T38420274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buffalo and Fort Erie Public Bridge Authority |
E903208
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public bridge authority |
C31127
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: public bridge authority Context triple: [Buffalo and Fort Erie Public Bridge Authority, instanceOf, public bridge authority]
-
A.
bridge authority
chosen
A bridge authority is an entity responsible for the planning, construction, operation, maintenance, and regulation of a bridge or network of bridges, including safety, tolling, and compliance with relevant laws and standards.
-
B.
private bridge
A private bridge is a non-publicly owned structure that spans a physical obstacle, such as a river or road, to provide controlled access exclusively for specific individuals, properties, or organizations.
-
C.
public library authority
A public library authority is an organization, typically established by a local or regional government, responsible for managing, funding, and overseeing public library services and resources for a defined community.
-
D.
public port authority
A public port authority is a government or quasi-governmental entity responsible for developing, managing, and regulating port facilities and maritime operations within a designated jurisdiction.
-
E.
SS authority
An SS authority is an individual or organizational entity within the Nazi Schutzstaffel (SS) hierarchy that exercised official power, control, and decision-making over security, policing, and ideological enforcement functions.
- F. None of above.
Provenance (1 batch)
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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.