Triple
T26947326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rama |
E678681
|
entity |
| Predicate | religionInhabitants |
P2986
|
FINISHED |
| Object | Christianity |
—
|
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: Christianity | Statement: [Rama, religionInhabitants, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionInhabitants Context triple: [Rama, religionInhabitants, Christianity]
-
A.
shareReligiousDemographics
Indicates that two entities have similar or identical distributions of religious affiliations within their populations.
-
B.
laterReligionDominant
Indicates that a religion adopted or followed at a later time becomes the dominant or primary religion in the relevant context or entity.
-
C.
religionInCountry
Indicates that a particular religion is practiced, present, or recognized within a specified country.
-
D.
mainAdherents
Indicates the primary group or groups that predominantly follow, support, or adhere to something (such as a belief, movement, or organization).
-
E.
dominantReligion
chosen
Indicates the religion that holds primary or majority status within a given group, region, or 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 27, 2026, 6:22 a.m.