Triple
T32627407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia (Buryatia, Kalmykia, Tuva) |
E834094
|
entity |
| Predicate | sharesReligiousTitle |
P37062
|
FINISHED |
| Object | Lama |
—
|
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: Lama | Statement: [Russia (Buryatia, Kalmykia, Tuva), sharesReligiousTitle, Lama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesReligiousTitle Context triple: [Russia (Buryatia, Kalmykia, Tuva), sharesReligiousTitle, Lama]
-
A.
religiousTitle
Indicates that one entity holds or is referred to by a specific religious rank, honorific, or clerical title in relation to another entity.
-
B.
titleHolderReligion
Indicates the religious affiliation associated with the holder of a particular title.
-
C.
sharesReligionWith
chosen
Indicates that two entities follow or are associated with the same religion or religious tradition.
-
D.
religiousName
Indicates that an entity has or is known by a name specifically associated with a religious role, identity, or context.
-
E.
namedAfterReligion
Indicates that an entity’s name is derived from or inspired by a particular religion or religious tradition.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: May 1, 2026, 1:06 a.m.