Triple
T38660531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Buddhist Temple (Kushinagar) |
E940320
|
entity |
| Predicate | servesDevoteesFrom |
P111925
|
FINISHED |
| Object | China |
—
|
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: China | Statement: [Chinese Buddhist Temple (Kushinagar), servesDevoteesFrom, China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesDevoteesFrom Context triple: [Chinese Buddhist Temple (Kushinagar), servesDevoteesFrom, China]
-
A.
receivesDevoteesFrom
chosen
Indicates that an entity (such as a place, person, or institution) is the destination to which devotees come or are directed from another entity.
-
B.
devoteesSeek
Indicates that devoted followers actively seek out, pursue, or strive to approach the object of their devotion.
-
C.
devoteesPrayFor
Indicates that devoted followers direct prayers or supplications toward a person, entity, or cause on its behalf.
-
D.
offersPrasadam
Indicates that one entity provides or distributes consecrated food (prasadam) to another entity.
-
E.
devotionPracticedBy
Indicates that a particular form of devotion, worship, or religious practice is performed or carried out by a specified agent or practitioner.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00ae638fcc819096537b2c21366161 |
completed | May 10, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_6a00ae0551988190bcb3564ed9af2847 |
completed | May 10, 2026, 4:10 p.m. |
Created at: May 3, 2026, 4:33 p.m.