Triple
T27903418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muktinath |
E705701
|
entity |
| Predicate | sacredToCommunity |
P8131
|
FINISHED |
| Object | Buddhists |
—
|
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: Buddhists | Statement: [Muktinath, sacredToCommunity, Buddhists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredToCommunity Context triple: [Muktinath, sacredToCommunity, Buddhists]
-
A.
sacredTo
chosen
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
B.
sacredStatus
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
-
C.
sacredHill
Indicates that a hill holds religious or spiritual significance within a belief system or tradition.
-
D.
religiousCommunityServed
Indicates the religious community or faith group that is served, ministered to, or supported by an entity or individual.
-
E.
sacredBoundary
Indicates a boundary that is regarded as holy or inviolable and therefore must not be crossed, altered, or violated.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:43 p.m.