Triple
T33156959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillsdale, Kansas |
E848604
|
entity |
| Predicate | recreationalAreaNearby |
P68166
|
FINISHED |
| Object | Hillsdale 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: Hillsdale State Park | Statement: [Hillsdale, Kansas, recreationalAreaNearby, Hillsdale State Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationalAreaNearby Context triple: [Hillsdale, Kansas, recreationalAreaNearby, Hillsdale State Park]
-
A.
hasRecreationalActivityNearby
Indicates that a location has one or more recreational activities or facilities available in its nearby surroundings.
-
B.
hasRecreationalUseNearby
chosen
Indicates that there is at least one location or facility for recreational activities situated close to the referenced entity.
-
C.
nearbyResortArea
Indicates that a resort area is located close to or within a short distance of a specified place or entity.
-
D.
recreationLocation
Indicates the place where a recreational activity or leisure pursuit occurs.
-
E.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:28 a.m.