Triple
T9687077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn by The Narrows |
E234437
|
entity |
| Predicate | waterBodyTypeBordered |
P1011
|
FINISHED |
| Object | tidal strait |
—
|
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: tidal strait | Statement: [Brooklyn by The Narrows, waterBodyTypeBordered, tidal strait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyTypeBordered Context triple: [Brooklyn by The Narrows, waterBodyTypeBordered, tidal strait]
-
A.
connectedBodyOfWater
Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
-
B.
waterbodyType
chosen
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
C.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
D.
isInlandWaterBodyOf
Indicates that one water body is an inland (non-oceanic) water feature that is geographically part of, contained within, or associated with another entity.
-
E.
waterbodyRegion
Indicates that a water body is located within, associated with, or spans a particular geographic region.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9cd42cc081909abcf4c85592d950 |
completed | April 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.