Triple
T14985508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thiksey Monastery |
E373689
|
entity |
| Predicate | GustorFestivalFeatures |
P96461
|
FINISHED |
| Object | masked dances |
—
|
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: masked dances | Statement: [Thiksey Monastery, GustorFestivalFeatures, masked dances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GustorFestivalFeatures Context triple: [Thiksey Monastery, GustorFestivalFeatures, masked dances]
-
A.
festivalFeature
chosen
Indicates that a festival includes or showcases a particular element, activity, or attraction as one of its features.
-
B.
festivalFocus
Indicates that a festival is centered around, dedicated to, or thematically focused on a particular subject, activity, or feature.
-
C.
festivalAttracts
Indicates that a festival draws or brings in attendees, participants, or interest toward itself.
-
D.
exampleFestival
Indicates that an entity is an instance or example of a particular festival event or type of festival.
-
E.
mainFestival
Indicates that an event is the primary or central festival associated with a particular context, place, or 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6ff4a7c8190ab7554f3a1a09b67 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:52 a.m.