Triple
T27798039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norbulingka |
E702168
|
entity |
| Predicate | culturalFestivalHeld |
P2955
|
FINISHED |
| Object | Shoton Festival |
—
|
NE NERFINISHED |
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: Shoton Festival | Statement: [Norbulingka, culturalFestivalHeld, Shoton Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalFestivalHeld Context triple: [Norbulingka, culturalFestivalHeld, Shoton Festival]
-
A.
festivalHeldIn
Indicates that a festival takes place or is hosted at a specific location or venue.
-
B.
hasCulturalEvent
chosen
Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given entity.
-
C.
festivalHeldOnOrAround
Indicates that a festival customarily takes place on or near a specified date or time period.
-
D.
shareCulturalFestivals
Indicates that two or more entities participate in or observe the same cultural festivals or celebrations.
-
E.
festivalActivity
Indicates that an entity is an event, performance, or engagement that takes place as part of a festival’s organized program.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 5:32 p.m.