Triple
T37737540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kushinara |
E940314
|
entity |
| Predicate | oneOfFourHolySitesAlongWith |
P183908
|
FINISHED |
| Object | Lumbini |
—
|
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: Lumbini | Statement: [Kushinara, oneOfFourHolySitesAlongWith, Lumbini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfFourHolySitesAlongWith Context triple: [Kushinara, oneOfFourHolySitesAlongWith, Lumbini]
-
A.
holiestSiteIn
Indicates that a site is considered the most sacred or religiously significant location within a particular place or region.
-
B.
holyCityAlongWith
chosen
Indicates that one entity is recognized or designated as a holy city together with, or in association with, another entity.
-
C.
isPlaceOfPilgrimageFor
Indicates that a location serves as a destination for religious or spiritual pilgrimage for a person or group.
-
D.
pilgrimageStartingPoint
Indicates the location from which a pilgrimage journey is initiated or begins.
-
E.
hasSpiritualSitesIn
Indicates that one entity possesses or contains spiritual or religious sites located within the boundaries of another entity.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.