Triple
T38018770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaya |
E948564
|
entity |
| Predicate | nearestMajorBuddhistSite |
P61457
|
FINISHED |
| Object | Mahabodhi Temple at Bodh Gaya |
—
|
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: Mahabodhi Temple at Bodh Gaya | Statement: [Gaya, nearestMajorBuddhistSite, Mahabodhi Temple at Bodh Gaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorBuddhistSite Context triple: [Gaya, nearestMajorBuddhistSite, Mahabodhi Temple at Bodh Gaya]
-
A.
nearReligiousSite
Indicates that one entity is located close to or in the immediate vicinity of a religious site.
-
B.
hasNearbyPilgrimageSite
chosen
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
C.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
-
D.
nearbyRoyalSite
Indicates that one place or object is located close to a site associated with royalty, such as a palace, castle, or royal residence.
-
E.
mainMonasteryLocation
Indicates the place where a religious order’s primary or central monastery is situated.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:20 p.m.