Triple
T33262695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pride of the Plains |
E851559
|
entity |
| Predicate | hasVisitorExperienceType |
P5308
|
FINISHED |
| Object | outdoor viewing exhibit |
—
|
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: outdoor viewing exhibit | Statement: [Pride of the Plains, hasVisitorExperienceType, outdoor viewing exhibit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorExperienceType Context triple: [Pride of the Plains, hasVisitorExperienceType, outdoor viewing exhibit]
-
A.
hasTypeOfVisitorExperience
chosen
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
-
B.
hasVisitorType
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
C.
hasCheckInExperience
Indicates that an entity has undergone, participated in, or possesses a record of a check-in process or event.
-
D.
hasVisitorActivities
Indicates that a place or entity offers or is associated with specific activities available for visitors to engage in.
-
E.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 1, 2026, 1:32 a.m.