Triple
T3106624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mad River (Ohio) |
E64845
|
entity |
| Predicate | hasRecreationSiteType |
P44008
|
FINISHED |
| Object | public access points |
—
|
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: public access points | Statement: [Mad River (Ohio), hasRecreationSiteType, public access points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationSiteType Context triple: [Mad River (Ohio), hasRecreationSiteType, public access points]
-
A.
hasRecreationType
Indicates that an entity is associated with or offers a particular type or category of recreational activity.
-
B.
hasRecreationClassification
chosen
Indicates that an entity is assigned a specific type or category of recreational use or activity.
-
C.
hasRecreationFacility
Indicates that one entity provides, contains, or is equipped with a recreational facility for use by another entity or by the public.
-
D.
hasRecreationActivity
Indicates that an entity provides, includes, or is associated with a particular recreational activity.
-
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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29d4aa8819093287bc71370fc05 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.