Triple
T38341524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somba Opu |
E1041418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fortified palace complex |
C38964
|
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: fortified palace complex Context triple: [Somba Opu, instanceOf, fortified palace complex]
-
A.
fortified royal residence
chosen
A fortified royal residence is a heavily defended, often grand architectural complex that serves both as the sovereign’s primary dwelling and as a stronghold for protecting the ruler, court, and seat of power.
-
B.
royal palace complex
A royal palace complex is an expansive, architecturally unified ensemble of residences, ceremonial halls, administrative buildings, gardens, and supporting structures that together serve as the political, cultural, and domestic center of a monarchy.
-
C.
monumental complex
A monumental complex is a large-scale, architecturally unified grouping of significant structures and spaces—such as temples, palaces, plazas, or memorials—designed to serve major ceremonial, political, religious, or commemorative functions.
-
D.
ceremonial palace
A ceremonial palace is a grand, often architecturally elaborate residence or complex designed primarily for hosting formal state rituals, official receptions, and symbolic public events.
-
E.
palace and park ensemble
A palace and park ensemble is a unified architectural and landscape complex where a grand residence is integrated with designed gardens, water features, and surrounding grounds to form a cohesive cultural and aesthetic whole.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.