Triple
T38303177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoo360 animal trail system |
E1032275
|
entity |
| Predicate | benefitToVisitors |
P132334
|
FINISHED |
| Object | overhead animal 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: overhead animal viewing | Statement: [Zoo360 animal trail system, benefitToVisitors, overhead animal viewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitToVisitors Context triple: [Zoo360 animal trail system, benefitToVisitors, overhead animal viewing]
-
A.
consequenceForVisitors
chosen
Indicates a resulting effect, outcome, or implication that an action, rule, or condition has specifically for visitors.
-
B.
attractsTypeOfVisitor
Indicates that an entity draws or appeals to a particular kind or category of visitor.
-
C.
visitorExperienceGoal
Indicates the intended outcome or quality of experience that an entity aims to provide for its visitors.
-
D.
primaryVisitors
Indicates that certain entities are the main or most important visitors associated with another entity or context.
-
E.
visitorCenter
Indicates that a location serves as a visitor center for a place, providing information or services to visitors of that place.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.