Triple
T412809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stone of Hope |
E9526
|
entity |
| Predicate | visitorExperience |
P5308
|
FINISHED |
| Object | walkway passes through the sculpture |
—
|
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: walkway passes through the sculpture | Statement: [Stone of Hope, visitorExperience, walkway passes through the sculpture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorExperience Context triple: [Stone of Hope, visitorExperience, walkway passes through the sculpture]
-
A.
visitorCenter
Indicates that a location serves as a visitor center for a place, providing information or services to visitors of that place.
-
B.
hasTypeOfVisitorExperience
chosen
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
-
C.
experiences
Indicates that an entity undergoes, feels, or is affected by a particular event, state, or condition.
-
D.
visitorCount
Indicates the number of visitors associated with a particular entity, context, or time period.
-
E.
isMajorAttractionFor
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecdc422881908910428fd1aee7c6 |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e9749234819084b0ce94faabd0b1 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.