Triple
T26627988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chester–Bridgeport Ferry |
E668409
|
entity |
| Predicate | riverBankTerminus |
P165358
|
FINISHED |
| Object | Chester riverfront |
—
|
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: Chester riverfront | Statement: [Chester–Bridgeport Ferry, riverBankTerminus, Chester riverfront]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverBankTerminus Context triple: [Chester–Bridgeport Ferry, riverBankTerminus, Chester riverfront]
-
A.
riverBankOne
Indicates that the referenced entity is one specific side or bank of a river, typically the first or primary one in a pairwise relation.
-
B.
riverBankTwo
Indicates a relationship where something is located on or associated with the second of two identified banks of a river.
-
C.
riverBankArea
Indicates the area of land adjacent to a riverbank associated with the given entity or location.
-
D.
riverBankWest
Indicates that something is located on or associated with the western bank of a river.
-
E.
riverBankLocality
Indicates that a locality is situated on or directly adjacent to the bank of a river.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 27, 2026, 2:23 a.m.