Triple
T16862244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Stalacpipe Organ |
E409942
|
entity |
| Predicate | tourExperience |
P89272
|
FINISHED |
| Object | music played automatically or by guide |
—
|
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: music played automatically or by guide | Statement: [Great Stalacpipe Organ, tourExperience, music played automatically or by guide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourExperience Context triple: [Great Stalacpipe Organ, tourExperience, music played automatically or by guide]
-
A.
experiences
Indicates that an entity undergoes, feels, or is affected by a particular event, state, or condition.
-
B.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
C.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
-
D.
providesExperienceOf
chosen
Indicates that one entity enables or delivers the experience of another entity to someone or something.
-
E.
tourDocumented
Indicates that a tour has been recorded or documented, typically capturing its details, events, or progression.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b50488fc8190b3b646543c3ba476 |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.