Triple
T28483650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fossil Butte National Monument |
E720764
|
entity |
| Predicate | hasVisitorCenterFeature |
P177315
|
FINISHED |
| Object | fossil preparation lab viewing area |
—
|
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: fossil preparation lab viewing area | Statement: [Fossil Butte National Monument, hasVisitorCenterFeature, fossil preparation lab viewing area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorCenterFeature Context triple: [Fossil Butte National Monument, hasVisitorCenterFeature, fossil preparation lab viewing area]
-
A.
hasVisitorCenterBy
Indicates that a location or site is served or administered by a specific visitor center.
-
B.
hasVisitorCenterIn
Indicates that an entity operates or possesses a visitor center located within a specified place.
-
C.
hasPublicVisitorsCenter
Indicates that an entity operates or provides access to a visitors center that is open to the general public.
-
D.
visitorCenter
Indicates that a location serves as a visitor center for a place, providing information or services to visitors of that place.
-
E.
visitorCentreName
Indicates the name assigned to a particular visitor centre.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: April 28, 2026, 2:57 a.m.