Triple
T25317788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bird Island (Algoa Bay) |
E634794
|
entity |
| Predicate | hasSurroundingWatersWithSpecies |
P12485
|
FINISHED |
| Object | dolphins |
—
|
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: dolphins | Statement: [Bird Island (Algoa Bay), hasSurroundingWatersWithSpecies, dolphins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingWatersWithSpecies Context triple: [Bird Island (Algoa Bay), hasSurroundingWatersWithSpecies, dolphins]
-
A.
hasSurroundingWaters
Indicates that one entity is bordered or encircled by bodies of water associated with another entity.
-
B.
hasSurroundingWatersStatus
Indicates whether and how an entity is characterized in terms of the presence, type, or condition of waters that surround it.
-
C.
hasAquaticEcosystem
Indicates that an entity possesses, contains, or is associated with an ecosystem primarily based in water (such as rivers, lakes, wetlands, or oceans).
-
D.
hasSurroundingWatersUsedFor
Indicates that the surrounding waters of a place or area are utilized for a specific purpose or activity.
-
E.
hasMarineSpecies
chosen
Indicates that an entity contains, supports, or is associated with one or more marine species.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 21, 2026, 1:28 p.m.