Triple
T28704902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylorsville Lake |
E729666
|
entity |
| Predicate | stateParkOnShore |
P49592
|
FINISHED |
| Object | Taylorsville Lake State Park |
—
|
NE NERFINISHED |
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: Taylorsville Lake State Park | Statement: [Taylorsville Lake, stateParkOnShore, Taylorsville Lake State Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateParkOnShore Context triple: [Taylorsville Lake, stateParkOnShore, Taylorsville Lake State Park]
-
A.
isCoastalPark
Indicates that a park is located along or directly adjacent to a coastline.
-
B.
isCoastalLandmarkOf
Indicates that a landmark is located on or very near the coast of a specified geographic area or body of water.
-
C.
stateParkLocation
chosen
Indicates that a state park is located within or associated with a specific geographic place or administrative region.
-
D.
isCoastalDestinationFor
Indicates that a place serves as a seaside or ocean-adjacent travel destination for a particular person, group, or market.
-
E.
stateParkSystem
Indicates that an entity is part of, managed by, or associated with a state-level park system or network of state parks.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 28, 2026, 5:44 a.m.