Triple
T33175327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockton Springs, Maine |
E849151
|
entity |
| Predicate | parkFeature |
P176154
|
FINISHED |
| Object | picnic areas at Fort Point State Park |
—
|
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: picnic areas at Fort Point State Park | Statement: [Stockton Springs, Maine, parkFeature, picnic areas at Fort Point State Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkFeature Context triple: [Stockton Springs, Maine, parkFeature, picnic areas at Fort Point State Park]
-
A.
parkArea
Indicates that an area of land is designated and used as a park or recreational green space.
-
B.
parkType
Indicates the specific category or classification of a park based on its designated use, management, or characteristics.
-
C.
parkIcon
Indicates that an entity is represented or marked with an icon denoting a park.
-
D.
parkSection
Indicates a relationship where a specific area or subsection belongs to, is contained within, or is designated as part of a larger park.
-
E.
parkAreaType
Indicates the classification of a park’s area according to its designated type or functional category.
- F. None of above. chosen
Provenance (4 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_69f3495d06508190b0b7729982982cea |
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. |
| PDg | Predicate description generation | batch_69f6dd3b335481909e24d4eb5b0269f9 |
completed | May 3, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:29 a.m.