Triple
T3530803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hathaway Bridge |
E74653
|
entity |
| Predicate | crossesBodyOfWaterType |
P15424
|
FINISHED |
| Object | bay |
—
|
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: bay | Statement: [Hathaway Bridge, crossesBodyOfWaterType, bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesBodyOfWaterType Context triple: [Hathaway Bridge, crossesBodyOfWaterType, bay]
-
A.
crossesWaterBody
chosen
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
-
B.
crossesWatershed
Indicates that one entity passes from one drainage basin or watershed area into another, traversing the boundary between them.
-
C.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
D.
waterTransport
Indicates the movement or conveyance of something from one place to another via water-based means such as rivers, seas, or other aquatic routes.
-
E.
connectsBodyOfWater
Indicates a relationship where one entity serves as a link or passage between two bodies of water, allowing them to be joined or interact.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc988ee081909c6b9d5eed0d2d6d |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.