Triple
T36143550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konkani people |
E1045379
|
entity |
| Predicate | religiousPluralism |
P42376
|
FINISHED |
| Object | multi-religious community |
—
|
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: multi-religious community | Statement: [Konkani people, religiousPluralism, multi-religious community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousPluralism Context triple: [Konkani people, religiousPluralism, multi-religious community]
-
A.
religiousSpectrum
Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
-
B.
religionDiversity
chosen
Indicates the degree to which multiple distinct religions are present and represented within a given context or group.
-
C.
isMultiReligious
Indicates that an entity is associated with or practices multiple religions rather than adhering to just one.
-
D.
religiousCounterpart
Indicates that one entity serves as the religious equivalent or analogue of another entity within a different belief system or tradition.
-
E.
religiousAttitude
Indicates an entity’s stance, disposition, or orientation toward religion or religious beliefs.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:08 p.m.