Triple
T204347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Bermuda |
E4576
|
entity |
| Predicate | reefRepresents |
P10238
|
FINISHED |
| Object | hazardous reefs around 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: hazardous reefs around Bermuda | Statement: [Coat of arms of Bermuda, reefRepresents, hazardous reefs around Bermuda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reefRepresents Context triple: [Coat of arms of Bermuda, reefRepresents, hazardous reefs around Bermuda]
-
A.
isShallowSea
Indicates that a body of water is a shallow marine area, typically near coasts or continental shelves, rather than deep ocean.
-
B.
seafloorType
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
-
C.
stateFish
Indicates that an entity is a fish that serves as the official state fish of a particular political region.
-
D.
marineArea
Indicates a relationship where an entity is located in, associated with, or relevant to a specific marine or oceanic area.
-
E.
coastType
Indicates the specific kind or classification of a coastline associated with a geographic 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25f4602c081909e89de233cbc5670 |
completed | Feb. 28, 2026, 3:21 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.