Triple
T29157916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mecosta County Park system |
E739103
|
entity |
| Predicate | offersSeason |
P99245
|
FINISHED |
| Object | summer recreation |
—
|
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: summer recreation | Statement: [Mecosta County Park system, offersSeason, summer recreation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersSeason Context triple: [Mecosta County Park system, offersSeason, summer recreation]
-
A.
hasSeasonalOffering
chosen
Indicates that an entity provides or features a special offering that is available only during a particular season or time of year.
-
B.
promotionSeason
Indicates the specific season or time period during which a promotion or promotional campaign is active.
-
C.
offersObject
Indicates that a subject provides or makes available a specific object to another party as an offer.
-
D.
offersEdition
Indicates that one entity provides or makes available a particular version or edition of another entity.
-
E.
hasSeasonalPromotions
Indicates that an entity offers promotions or special deals that occur during specific seasons or time-limited periods.
- 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 28, 2026, 11:46 a.m.