Triple
T8559736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamunotri Temple |
E202659
|
entity |
| Predicate | closesDuring |
P12551
|
FINISHED |
| Object | heavy winter snowfall |
—
|
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: heavy winter snowfall | Statement: [Yamunotri Temple, closesDuring, heavy winter snowfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closesDuring Context triple: [Yamunotri Temple, closesDuring, heavy winter snowfall]
-
A.
closedDuring
chosen
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
-
B.
closureFrequency
Indicates how often a particular process, event, or entity is closed or brought to an end within a given period.
-
C.
closingTime
Indicates the specific time at which a place, service, or activity stops operating or becomes unavailable.
-
D.
closedAfterEvent
Indicates that an entity becomes or is marked as closed following the occurrence of a specified event.
-
E.
closingPosition
Indicates that an entity terminates, finalizes, or brings to an end the position or state of another 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe949974c8190a75d9c767ca5fa5a |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.