Triple
T23996813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Cay |
E605212
|
entity |
| Predicate | hasSurroundingWatersUsedFor |
P154559
|
FINISHED |
| Object | fishing |
—
|
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: fishing | Statement: [East Cay, hasSurroundingWatersUsedFor, fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingWatersUsedFor Context triple: [East Cay, hasSurroundingWatersUsedFor, fishing]
-
A.
hasNearbyWatersUsedBy
Indicates that a body of water located near an entity is utilized or accessed by another specified entity.
-
B.
hasSurroundingWaters
Indicates that one entity is bordered or encircled by bodies of water associated with another entity.
-
C.
hasSurroundingWatersStatus
Indicates whether and how an entity is characterized in terms of the presence, type, or condition of waters that surround it.
-
D.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
E.
hasShelteredWaters
Indicates that one location provides protected or calm waters for another location or activity, shielding it from rough or open conditions.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38f8a208190a293c64b9c9202c0 |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e35944c8190b57cfa31f1e9da1b |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:38 p.m.