Triple
T5021180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan Qaboos Grand Mosque |
E112850
|
entity |
| Predicate | hasPrayerHallCapacity |
P47633
|
FINISHED |
| Object | about 6500 worshippers in main 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: about 6500 worshippers in main hall | Statement: [Sultan Qaboos Grand Mosque, hasPrayerHallCapacity, about 6500 worshippers in main hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrayerHallCapacity Context triple: [Sultan Qaboos Grand Mosque, hasPrayerHallCapacity, about 6500 worshippers in main hall]
-
A.
prayerHallCapacity
chosen
Indicates the maximum number of people that the prayer hall is designed or allowed to accommodate at one time.
-
B.
hasNumberOfMosques
Indicates the quantity of mosques associated with a given entity.
-
C.
hasMosque
Indicates that one entity possesses, contains, or is the location of a mosque.
-
D.
mainPrayerHallType
Indicates the specific architectural or functional type assigned to a main prayer hall within a religious or worship-related structure.
-
E.
hasMinarets
Indicates that an entity (typically a building) possesses one or more minarets as architectural features.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd736399ac8190aa38efc4b4edc6a2 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.