Triple
T11828454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanded Sahib |
E281317
|
entity |
| Predicate | religiousStructureDensity |
P95507
|
FINISHED |
| Object | numerous gurdwaras |
—
|
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: numerous gurdwaras | Statement: [Nanded Sahib, religiousStructureDensity, numerous gurdwaras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousStructureDensity Context triple: [Nanded Sahib, religiousStructureDensity, numerous gurdwaras]
-
A.
hasReligiousBuildingDensity
chosen
Indicates the degree to which religious buildings are concentrated within a given area or region.
-
B.
majorityReligionInUrbanAreas
Indicates that a specified religion is the predominant or most widely practiced faith within the urban areas of a given region or population.
-
C.
religionSignificantMinorityRegion
Indicates that a particular religion constitutes a significant minority presence within a specified geographic region.
-
D.
inReligiousStructure
Indicates that one entity is located within or inside a building or structure used for religious purposes.
-
E.
dominantReligion
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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5ec3a148190bb184ba0d481b16a |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.