Triple
T5274945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Javanese people of Suriname |
E119350
|
entity |
| Predicate | significantReligionInstitution |
P45706
|
FINISHED |
| Object | mosques |
—
|
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: mosques | Statement: [Javanese people of Suriname, significantReligionInstitution, mosques]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantReligionInstitution Context triple: [Javanese people of Suriname, significantReligionInstitution, mosques]
-
A.
religionSignificant
Indicates that a particular religion plays an important or influential role in relation to the referenced entity or context.
-
B.
religiousFoundation
Indicates that an entity was established, created, or founded by a religious organization, authority, or tradition.
-
C.
religiousHouse
chosen
Indicates that an entity is a religious institution or building used for worship, residence, or activities of a religious community.
-
D.
hasReligiousInstitutionType
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
-
E.
foundedReligion
Indicates that an entity established or originated a particular religion.
- 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7c23bed88190b406dee21957d823 |
completed | March 20, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69bd77c83d1c8190bd8b9616113d413c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.