Triple
T31805401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umm Rashrash |
E811857
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman military outpost |
C13727
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Ottoman military outpost Context triple: [Umm Rashrash, instanceOf, Ottoman military outpost]
-
A.
Ottoman imperial pavilion
An Ottoman imperial pavilion is a richly decorated, often freestanding structure within palace or garden complexes, used by sultans and the court for leisure, ceremonies, and receptions, showcasing refined Ottoman architectural and artistic traditions.
-
B.
Sasanian frontier stronghold
A Sasanian frontier stronghold is a fortified military installation positioned along the empire’s borders to control strategic routes, monitor enemy movements, and defend against incursions.
-
C.
fortified settlement
chosen
A fortified settlement is a community enclosed by defensive structures such as walls, ramparts, or palisades, designed to protect its inhabitants and resources from external threats.
-
D.
Ottoman religious complex
An Ottoman religious complex is an architectural ensemble centered around a mosque and typically including facilities such as a madrasa, hospice, bath, and charitable institutions, designed to serve the spiritual, educational, and social needs of the community.
-
E.
Ottoman government office
An Ottoman government office is an administrative institution within the Ottoman Empire responsible for managing specific state functions such as taxation, justice, military affairs, or provincial governance under the authority of the sultan and central bureaucracy.
- F. None of above.
Provenance (1 batch)
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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:42 p.m.