Triple
T2276661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Pilgrimage Festivals |
E50785
|
entity |
| Predicate | statusInTemplePeriod |
P36511
|
FINISHED |
| Object | major festivals |
—
|
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: major festivals | Statement: [Three Pilgrimage Festivals, statusInTemplePeriod, major festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInTemplePeriod Context triple: [Three Pilgrimage Festivals, statusInTemplePeriod, major festivals]
-
A.
templeOpening
Indicates that a temple begins operating or becomes accessible for worship, visitation, or related activities.
-
B.
lastMajorTempleClosed
Indicates the time or event at which the final significant temple associated with an entity was permanently closed.
-
C.
statusAfterTempleDestruction
Indicates the condition or state of an entity that applies specifically after the destruction of the temple.
-
D.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
E.
hadTempleDedicatedTo
Indicates that a temple was formally dedicated in honor of, or for the worship of, a particular entity.
- F. None of above. chosen
Provenance (4 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1ecc600819095dd4f69af1d18d8 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:48 p.m.