Triple
T5860327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yavuz Selim Mosque |
E130258
|
entity |
| Predicate | hasPrayerHallPlan |
P53929
|
FINISHED |
| Object | single-dome hall |
—
|
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: single-dome hall | Statement: [Yavuz Selim Mosque, hasPrayerHallPlan, single-dome hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrayerHallPlan Context triple: [Yavuz Selim Mosque, hasPrayerHallPlan, single-dome hall]
-
A.
hasMosque
Indicates that one entity possesses, contains, or is the location of a mosque.
-
B.
mainPrayerHallType
chosen
Indicates the specific architectural or functional type assigned to a main prayer hall within a religious or worship-related structure.
-
C.
hasMihrab
Indicates that a structure or space contains or is equipped with a mihrab, the niche indicating the direction of prayer in a mosque or Islamic prayer area.
-
D.
hasMinarets
Indicates that an entity (typically a building) possesses one or more minarets as architectural features.
-
E.
architecturalPlanner
Indicates a relationship where an entity is responsible for designing, organizing, or planning the architectural structure or layout of another entity.
- 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_69c0084f3bb08190a7720f55f7aa4252 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:56 p.m.