Triple
T31452631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batna |
E802363
|
entity |
| Predicate | mainReligionBuildingType |
P92816
|
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: [Batna, mainReligionBuildingType, mosque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainReligionBuildingType Context triple: [Batna, mainReligionBuildingType, mosque]
-
A.
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.
-
B.
religiousBuildingInstanceOf
chosen
Indicates that a specific religious building is an instance of a particular class or type of religious building.
-
C.
inReligiousStructure
Indicates that one entity is located within or inside a building or structure used for religious purposes.
-
D.
religionBuildingDenomination
Indicates the specific religious denomination with which a religious building is affiliated or to which it belongs.
-
E.
isMajorReligiousBuildingOf
Indicates that a building serves as the primary or most significant religious structure associated with a particular religious group, institution, or area.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 9:14 p.m.