Triple
T4306603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferry Building |
E99968
|
entity |
| Predicate | declineInFerryTrafficAfter |
P55042
|
FINISHED |
| Object | opening of Bay 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: opening of Bay Bridge | Statement: [Ferry Building, declineInFerryTrafficAfter, opening of Bay Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declineInFerryTrafficAfter Context triple: [Ferry Building, declineInFerryTrafficAfter, opening of Bay Bridge]
-
A.
eraOfMajorUseAsFerryTerminal
Indicates the time period during which a location was primarily used as a ferry terminal.
-
B.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
C.
hasNumberOfFerrySlips
Indicates the specific count of ferry slips associated with or available at a given entity.
-
D.
hasFerryPort
Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
-
E.
hasFerryType
Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
- F. None of above. chosen
Provenance (4 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350bb78cc8190a850aca47d8711cf |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b347ff45cc8190b0cc335a94cc3d73 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e06b3ec81909298b1ddd74d37bd |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:09 p.m.