Triple
T38018965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manpur |
E948570
|
entity |
| Predicate | hasReligiousSignificanceViaProximityTo |
P29505
|
FINISHED |
| Object | Bodh Gaya |
E167993
|
NE 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: Bodh Gaya | Statement: [Manpur, hasReligiousSignificanceViaProximityTo, Bodh Gaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousSignificanceViaProximityTo Context triple: [Manpur, hasReligiousSignificanceViaProximityTo, Bodh Gaya]
-
A.
hasReligiousSignificanceVia
Indicates that something holds religious significance specifically by means of, or through the mediation of, another entity, event, or context.
-
B.
hasReligiousSignificanceDuring
Indicates that something holds particular religious meaning, importance, or sacred relevance specifically during a given time period, event, or occasion.
-
C.
nearReligiousSite
chosen
Indicates that one entity is located close to or in the immediate vicinity of a religious site.
-
D.
regionOfReligiousSignificance
Indicates that a location or area holds recognized religious importance, such as being sacred, holy, or central to religious practices or beliefs.
-
E.
hasReligiousBuildingAlong
Indicates that a religious building is located along the course, path, or extent of the referenced entity.
- F. None of above.
Provenance (4 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_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4193b1b584819087944cdf47b26378 |
completed | June 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.