Triple
T15609089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemis Monastery |
E375238
|
entity |
| Predicate | festivalReligion |
P11809
|
FINISHED |
| Object | Buddhist festival |
—
|
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: Buddhist festival | Statement: [Hemis Monastery, festivalReligion, Buddhist festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalReligion Context triple: [Hemis Monastery, festivalReligion, Buddhist festival]
-
A.
religiousEvent
Indicates that an event is related to religious practices, observances, or ceremonies.
-
B.
religiousEventRecognizedBy
Indicates that a religious event is formally acknowledged, validated, or accepted by a particular authority, group, or institution.
-
C.
festivalObserved
Indicates that a particular festival is celebrated, observed, or commemorated by an entity (such as a person, group, or community).
-
D.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
E.
pilgrimageFestivalsObserved
chosen
Indicates that certain pilgrimage-related religious festivals are practiced or observed by the subject.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e8024948190a6c711f2e5c2aac4 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.