Triple
T2708593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clinch Park |
E59802
|
entity |
| Predicate | hasTypeOfWaterBody |
P1011
|
FINISHED |
| Object | bay shoreline |
—
|
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: bay shoreline | Statement: [Clinch Park, hasTypeOfWaterBody, bay shoreline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfWaterBody Context triple: [Clinch Park, hasTypeOfWaterBody, bay shoreline]
-
A.
hasAreaWaterBody
Indicates that an entity includes, contains, or is associated with a body of water within its area or boundaries.
-
B.
appliesToWaterBody
Indicates that something (such as a rule, condition, property, or effect) is relevant or applicable specifically to a particular water body.
-
C.
waterbodyType
chosen
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
D.
isFreshwaterBody
Indicates that the referenced body of water consists primarily of non-saline (fresh) water rather than saltwater.
-
E.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda7542548190bbf6c947145f7f63 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.