Triple
T33650220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parish of Sandys |
E862076
|
entity |
| Predicate | locatedAtEndOfArchipelago |
P206620
|
FINISHED |
| Object | western end of Bermuda |
—
|
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 end of Bermuda | Statement: [Parish of Sandys, locatedAtEndOfArchipelago, western end of Bermuda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtEndOfArchipelago Context triple: [Parish of Sandys, locatedAtEndOfArchipelago, western end of Bermuda]
-
A.
locatedInArchipelago
Indicates that one place or geographic entity is situated within or is part of a specific archipelago.
-
B.
locatedOnIslandOrPeninsula
Indicates that something is situated on an island or on a peninsula, rather than on a mainland area.
-
C.
locatedInRegionOfIsland
Indicates that an entity is situated within a specific region that is part of an island.
-
D.
launchArchipelago
Indicates initiating the coordinated start or deployment of multiple related components or entities as a unified group.
-
E.
locatedAtEndOfBeach
Indicates that something is positioned at the far end or terminal point of a beach relative to a reference direction or area.
- F. None of above. chosen
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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.