Triple
T23037566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parishes of Bermuda |
E573643
|
entity |
| Predicate | haveMaritimeBoundaries |
P39564
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Parishes of Bermuda, haveMaritimeBoundaries, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveMaritimeBoundaries Context triple: [Parishes of Bermuda, haveMaritimeBoundaries, true]
-
A.
sharesMaritimeBorders
chosen
Indicates that two entities have adjacent territorial waters or maritime zones that touch or overlap, forming a shared sea boundary.
-
B.
bordersStateAcrossSea
Indicates that one state is separated from another by a sea but still directly borders it across that body of water.
-
C.
hasLandBorderWithSea
Indicates that an entity’s land area directly borders or touches a sea along its coastline.
-
D.
maritimeBoundaryLengthApproxKm
Indicates the approximate length, measured in kilometers, of a state's maritime boundary or coastline.
-
E.
bordersCountryViaWaterway
Indicates that two countries share a boundary that is defined or connected by a waterway such as a river, canal, or strait.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f185111f0881908991fcd6cdc7db9f |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:53 p.m.