Triple
T18745647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jolo |
E458397
|
entity |
| Predicate | religiousInstitutionDominant |
P109749
|
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: [Jolo, religiousInstitutionDominant, mosques]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousInstitutionDominant Context triple: [Jolo, religiousInstitutionDominant, mosques]
-
A.
dominantReligion
Indicates the religion that holds primary or majority status within a given group, region, or entity.
-
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.
isMajorReligiousInstitutionIn
chosen
Indicates that a major religious institution (such as a church, mosque, temple, or similar body) is located within or primarily based in a specified place or region.
-
D.
religiousEnvironment
Indicates the religious context, atmosphere, or setting in which an entity exists or an action takes place.
-
E.
religiousInstitutionShared
Indicates that two entities are associated with or participate in the same religious institution or organization.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e57692c380819091e8a919ab6c9ca9 |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.