Triple
T19031235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharlika Village |
E465741
|
entity |
| Predicate | hasReligionCommunityCenter |
P1191
|
FINISHED |
| Object | mosque |
—
|
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: mosque | Statement: [Maharlika Village, hasReligionCommunityCenter, mosque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionCommunityCenter Context triple: [Maharlika Village, hasReligionCommunityCenter, mosque]
-
A.
hasPlaceOfWorship
chosen
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
B.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
C.
religiousCommunityServed
Indicates the religious community or faith group that is served, ministered to, or supported by an entity or individual.
-
D.
tookPlaceAtReligiousCenter
Indicates that an event or action occurred at a religious center or place of worship.
-
E.
associatedReligionBuilding
Indicates that there is a relationship between a religion and a specific building that is connected to, used by, or significant for that 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d7404d748190bcb51692fb822fd4 |
completed | April 20, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.