Triple
T28886721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uttara |
E732583
|
entity |
| Predicate | hasReligiousMotifs |
P24743
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Uttara, hasReligiousMotifs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousMotifs Context triple: [Uttara, hasReligiousMotifs, yes]
-
A.
hasReligiousTheme
chosen
Indicates that something (such as a work, event, or object) centrally involves or expresses religious ideas, symbols, practices, or narratives.
-
B.
hasReligiousRepresentation
Indicates that one entity serves as a religious symbol, figure, or embodiment for another entity or within a particular context.
-
C.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
D.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
-
E.
hasReligiousSignificanceVia
Indicates that something holds religious significance specifically by means of, or through the mediation of, another entity, event, or context.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: April 28, 2026, 7:51 a.m.