Triple
T33262746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slawson Family Tiger Trek |
E851561
|
entity |
| Predicate | visitorExperienceType |
P5308
|
FINISHED |
| Object | walk-through viewing |
—
|
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: walk-through viewing | Statement: [Slawson Family Tiger Trek, visitorExperienceType, walk-through viewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorExperienceType Context triple: [Slawson Family Tiger Trek, visitorExperienceType, walk-through viewing]
-
A.
visitorExperienceGoal
Indicates the intended outcome or quality of experience that an entity aims to provide for its visitors.
-
B.
hasTypeOfVisitorExperience
chosen
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
-
C.
visitorPractice
Indicates that a visitor engages in or performs a particular practice, activity, or routine.
-
D.
visitorService
Indicates a relationship where a service is provided specifically for or to visitors, such as assistance, information, or support during their visit.
-
E.
visitorCentreType
Indicates the specific kind or category of a visitor centre associated with an entity.
- 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_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:32 a.m.