Triple
T19563548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Oyster Bay |
E489517
|
entity |
| Predicate | separatedFromOceanBy |
P51104
|
FINISHED |
| Object | barrier islands |
—
|
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: barrier islands | Statement: [South Oyster Bay, separatedFromOceanBy, barrier islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatedFromOceanBy Context triple: [South Oyster Bay, separatedFromOceanBy, barrier islands]
-
A.
separatedFromByLand
chosen
Indicates that two entities are divided or kept apart from each other by an intervening landmass.
-
B.
separatedByOceanFrom
Indicates that two entities are located on different landmasses with an ocean lying between them as a separating barrier.
-
C.
seaSeparatedFrom
Indicates that one geographic region or landmass is separated from another by a sea lying between them.
-
D.
isSeparatedFromMainlandBy
Indicates that one land area is divided from the mainland by a specific intervening body or feature, such as water or terrain.
-
E.
separatedByInlandSea
Indicates that two land areas are divided from each other by an inland sea lying between them.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f75b2d481909fa3f603fe6bd5bd |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.