Triple
T37737628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahaparinirvana Temple |
E940316
|
entity |
| Predicate | hasStupaNearby |
P202539
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Mahaparinirvana Temple, hasStupaNearby, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStupaNearby Context triple: [Mahaparinirvana Temple, hasStupaNearby, Yes]
-
A.
hasStupa
Indicates that one entity possesses, contains, or features a stupa as part of its structure, property, or composition.
-
B.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
C.
hasNearbyShrine
Indicates that one entity is located close to or in the vicinity of a shrine associated with another entity.
-
D.
hasNearbyMonasteryLandingPoints
Indicates that there are designated landing points located close to a monastery.
-
E.
hasNearbyMonastery
Indicates that one entity is located close to or in the vicinity of a monastery.
- F. None of above. chosen
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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a008e29f76881908e656dbbd7fceea3 |
completed | May 10, 2026, 1:54 p.m. |
| PD | Predicate disambiguation | batch_6a008dc01b308190bc26e69814692f82 |
completed | May 10, 2026, 1:53 p.m. |
| PDg | Predicate description generation | batch_6a008e29394481909b8d124c8265141f |
completed | May 10, 2026, 1:54 p.m. |
Created at: May 3, 2026, 4:18 p.m.