Triple
T27644648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadia region |
E696676
|
entity |
| Predicate | religiousCenterType |
P34373
|
FINISHED |
| Object | center of Vaishnavite pilgrimage |
—
|
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: center of Vaishnavite pilgrimage | Statement: [Nadia region, religiousCenterType, center of Vaishnavite pilgrimage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousCenterType Context triple: [Nadia region, religiousCenterType, center of Vaishnavite pilgrimage]
-
A.
religiousServiceType
Indicates the specific kind or category of religious service associated with an event or context.
-
B.
religiousSiteType
chosen
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
C.
religiousBuildingInstanceOf
Indicates that a specific religious building is an instance of a particular class or type of religious building.
-
D.
religiousHouse
Indicates that an entity is a religious institution or building used for worship, residence, or activities of a religious community.
-
E.
religiousMovementType
Indicates the specific kind or category of religious movement with which an entity is associated.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 27, 2026, 2:28 p.m.