Triple
T8744513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Checkerboard Mesa |
E207789
|
entity |
| Predicate | hasParkServiceSign |
P85149
|
FINISHED |
| Object | Checkerboard Mesa viewpoint sign |
—
|
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: Checkerboard Mesa viewpoint sign | Statement: [Checkerboard Mesa, hasParkServiceSign, Checkerboard Mesa viewpoint sign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParkServiceSign Context triple: [Checkerboard Mesa, hasParkServiceSign, Checkerboard Mesa viewpoint sign]
-
A.
hasParkStatus
Indicates that an entity holds a particular designation or status related to being a park (e.g., national park, city park, protected parkland).
-
B.
hasParkAccess
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
-
C.
parkServed
Indicates that a particular park is provided with services or coverage by a specified entity (such as a transit line, facility, or administrative body).
-
D.
hasParking
Indicates that a place or facility provides designated parking space(s) available for use.
-
E.
hasParkOperator
Indicates that a park is operated or managed by a specific organization or individual.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d72e47c819099540d062d35ebd5 |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:38 p.m.