Triple
T37274155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taman Cahaya |
E924598
|
entity |
| Predicate | primaryReligionPracticed |
P2986
|
FINISHED |
| Object | Islam |
E1333
|
NE 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: Islam | Statement: [Taman Cahaya, primaryReligionPracticed, Islam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryReligionPracticed Context triple: [Taman Cahaya, primaryReligionPracticed, Islam]
-
A.
hostReligion
Indicates that an entity organizes, accommodates, or provides a venue for a particular religious group, event, or practice.
-
B.
declaredReligion
Indicates that an entity has formally stated or reported a particular religious affiliation.
-
C.
dominantReligion
chosen
Indicates the religion that holds primary or majority status within a given group, region, or entity.
-
D.
majorReligionCanBe
Indicates that an entity can have a particular major religion as one of its possible primary religious affiliations.
-
E.
laterReligionDominant
Indicates that a religion adopted or followed at a later time becomes the dominant or primary religion in the relevant context or entity.
- F. None of above.
Provenance (4 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a405133471c8190a6696bd08864b30a |
completed | June 27, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.