Triple
T26847100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Tibet |
E675954
|
entity |
| Predicate | religiousPilgrimageCenter |
P17002
|
FINISHED |
| Object | Lhasa |
—
|
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: Lhasa | Statement: [Central Tibet, religiousPilgrimageCenter, Lhasa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousPilgrimageCenter Context triple: [Central Tibet, religiousPilgrimageCenter, Lhasa]
-
A.
isPlaceOfPilgrimageFor
Indicates that a location serves as a destination for religious or spiritual pilgrimage for a person or group.
-
B.
pilgrimageStartingPoint
Indicates the location from which a pilgrimage journey is initiated or begins.
-
C.
spiritualCenterOf
chosen
Indicates that one entity serves as the primary locus or focal point of spiritual life, practice, or significance for another entity or group.
-
D.
pilgrimageAssociatedWith
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
E.
pilgrimagePractice
Indicates that an entity engages in, prescribes, or is associated with the religious act of undertaking a pilgrimage as a spiritual practice.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 27, 2026, 5:13 a.m.