Triple
T15930373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seneca Lake State Park |
E386309
|
entity |
| Predicate | shoreLocation |
P26064
|
FINISHED |
| Object | northern shore of Seneca Lake |
—
|
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: northern shore of Seneca Lake | Statement: [Seneca Lake State Park, shoreLocation, northern shore of Seneca Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoreLocation Context triple: [Seneca Lake State Park, shoreLocation, northern shore of Seneca Lake]
-
A.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
B.
shoreHas
Indicates that a shore possesses, contains, or is characterized by a particular feature, object, or attribute.
-
C.
shore
chosen
Indicates a relationship where one entity forms or lies along the edge or boundary of a body of water, such as a sea, lake, or river.
-
D.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
-
E.
connectsToCoastAt
Indicates that one entity has a direct physical or geographical connection or access to a coastline at the location of another 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.