Triple
T25498673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trikona Parikrama of Vindhyachal |
E639047
|
entity |
| Predicate | connectsSite |
P87888
|
FINISHED |
| Object | Vindhyavasini Devi Temple |
—
|
NE NERFINISHED |
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: Vindhyavasini Devi Temple | Statement: [Trikona Parikrama of Vindhyachal, connectsSite, Vindhyavasini Devi Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsSite Context triple: [Trikona Parikrama of Vindhyachal, connectsSite, Vindhyavasini Devi Temple]
-
A.
linkedSite
Indicates that one site has an explicit hyperlink or reference connection to another site.
-
B.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
-
C.
connectsSystem
Indicates that one system establishes a link or interface with another system, enabling interaction or data exchange between them.
-
D.
connectsLocation
Indicates a relationship where one entity serves as a link or route that joins or provides access between two locations.
-
E.
connectsReligiousSite
chosen
Indicates a relationship where something serves as a link, route, or association between one religious site and another.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 21, 2026, 2:41 p.m.