Triple
T36856894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stargazers Campground |
E910820
|
entity |
| Predicate | parkTypeContext |
P179321
|
FINISHED |
| Object | national park campground |
—
|
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: national park campground | Statement: [Stargazers Campground, parkTypeContext, national park campground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkTypeContext Context triple: [Stargazers Campground, parkTypeContext, national park campground]
-
A.
parkType
Indicates the specific category or classification of a park based on its designated use, management, or characteristics.
-
B.
parkAreaType
Indicates the classification of a park’s area according to its designated type or functional category.
-
C.
parkUnitType
chosen
Indicates the specific classification or category of a park unit (such as national park, monument, preserve, etc.) that characterizes the type of protected area it represents.
-
D.
parkFeature
Indicates that a particular feature, amenity, or element is part of, located within, or characteristic of a park.
-
E.
parkArea
Indicates that an area of land is designated and used as a park or recreational green space.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.