Triple
T24561270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oak Beach, New York |
E607659
|
entity |
| Predicate | coastalWaterBody |
P1778
|
FINISHED |
| Object | Great South Bay |
E396125
|
NE 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: Great South Bay | Statement: [Oak Beach, New York, coastalWaterBody, Great South Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalWaterBody Context triple: [Oak Beach, New York, coastalWaterBody, Great South Bay]
-
A.
connectedBodyOfWater
Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
-
B.
bodyOfWater
chosen
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
C.
landingBodyOfWater
Indicates that an entity (such as an aircraft or vessel) lands on or comes to rest upon a specified body of water.
-
D.
formsBodyOfWater
Indicates that one entity constitutes or creates the physical substance or structure that makes up a particular body of water.
-
E.
hasBodyOfWaterType
Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
- F. None of above.
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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f63a348190a3c9fd96e3ad80b0 |
completed | April 30, 2026, 12:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a100472823081909f7eead2c32ba3e1 |
completed | May 22, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.