Triple
T9773654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plucks Gutter |
E237189
|
entity |
| Predicate | nearbyWaterwayUse |
P44236
|
FINISHED |
| Object | recreational boating |
—
|
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: recreational boating | Statement: [Plucks Gutter, nearbyWaterwayUse, recreational boating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyWaterwayUse Context triple: [Plucks Gutter, nearbyWaterwayUse, recreational boating]
-
A.
hasNearbyWatersUsedBy
Indicates that a body of water located near an entity is utilized or accessed by another specified entity.
-
B.
usedWaterway
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
-
C.
waterwayFunction
Indicates the primary role or purpose that a waterway serves, such as transportation, irrigation, drainage, or recreation.
-
D.
nearbyWatercourse
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
E.
waterbodyUsedFor
chosen
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f6b8348190bd05b94519de9bc9 |
completed | April 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.