Triple
T5361583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salar |
E103032
|
entity |
| Predicate | traditionalReligionBuilding |
P45706
|
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: [Salar, traditionalReligionBuilding, mosque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalReligionBuilding Context triple: [Salar, traditionalReligionBuilding, mosque]
-
A.
religiousHouse
chosen
Indicates that an entity is a religious institution or building used for worship, residence, or activities of a religious community.
-
B.
religiousBuildingManaged
Indicates that one entity is responsible for overseeing, operating, or administering a religious building associated with another entity.
-
C.
religiousBuildingDesigned
Indicates that one entity (typically an architect or designer) is responsible for designing a religious building associated with the other entity.
-
D.
religionAtConstruction
Indicates the religion or religious tradition associated with something at the time it was constructed.
-
E.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865a0bb081909579cfe7c7974075 |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.