Triple
T24170699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Parishes of Bermuda |
E599120
|
entity |
| Predicate | positionWithinBermuda |
P16235
|
FINISHED |
| Object | western side |
—
|
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: western side | Statement: [Western Parishes of Bermuda, positionWithinBermuda, western side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithinBermuda Context triple: [Western Parishes of Bermuda, positionWithinBermuda, western side]
-
A.
positionRelativeToCoast
chosen
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
B.
locatedOnBarrierIsland
Indicates that something is situated on a barrier island, a coastal landform that lies parallel to the mainland and is separated from it by a body of water.
-
C.
locatedInBayOf
Indicates that something is situated within or directly on a specific bay.
-
D.
bayLocation
Indicates that an entity (such as a bay) is geographically located in or along a specified place or region.
-
E.
positionRelativeToSurfaceCurrents
Indicates the spatial relationship of an entity’s location or movement with respect to the direction and pattern of surface currents.
- 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_69e288cbd62881909de32ca64a70c17b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:33 p.m.