Triple
T7450188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badrinath |
E171987
|
entity |
| Predicate | templeClosingPeriod |
P32545
|
FINISHED |
| Object | typically closes around October or November |
—
|
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: typically closes around October or November | Statement: [Badrinath, templeClosingPeriod, typically closes around October or November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeClosingPeriod Context triple: [Badrinath, templeClosingPeriod, typically closes around October or November]
-
A.
templeClosing
chosen
Indicates that a temple ceases or is scheduled to cease its operations or public access, marking its closure.
-
B.
templeOpening
Indicates that a temple begins operating or becomes accessible for worship, visitation, or related activities.
-
C.
lastMajorTempleClosed
Indicates the time or event at which the final significant temple associated with an entity was permanently closed.
-
D.
statusInTemplePeriod
Indicates the role, condition, or standing that an entity held during the specified temple period.
-
E.
templePractice
Indicates a religious or ritual activity that is performed within or in connection with a temple.
- 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f38af3fc8190bc5c57ca89d976bc |
completed | March 27, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:14 p.m.