Triple
T27112743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Temple of Tinsukia |
E686757
|
entity |
| Predicate | languageOfLocalDevotees |
P136332
|
FINISHED |
| Object | Assamese |
—
|
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: Assamese | Statement: [Bell Temple of Tinsukia, languageOfLocalDevotees, Assamese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfLocalDevotees Context triple: [Bell Temple of Tinsukia, languageOfLocalDevotees, Assamese]
-
A.
languageOfDevotees
chosen
Indicates the language commonly used or spoken by a group of devotees in their religious or devotional practices.
-
B.
languageOfWorship
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
C.
languageOfReligion
Indicates the language in which a particular religion is traditionally expressed, practiced, or documented.
-
D.
devotionalLanguageType
Indicates the type or category of language used in a devotional or religious context.
-
E.
languageOfSurroundingCulture
Indicates that one entity is the language predominantly used or characteristic of the surrounding culture associated with 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 27, 2026, 8:54 a.m.