Triple
T14489928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughal riverfront gardens of Lahore |
E359333
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal garden complex |
C12406
|
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: Mughal garden complex Context triple: [Mughal riverfront gardens of Lahore, instanceOf, Mughal garden complex]
-
A.
palace and park ensemble
chosen
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.
-
B.
desert palace
A desert palace is a grand, often fortified residence or complex built within an arid landscape, designed to provide luxury, shade, and water-centered courtyards amid harsh climatic conditions.
-
C.
Timurid architectural ensemble
A Timurid architectural ensemble is a cohesive complex of buildings, spaces, and decorative elements that exemplifies the monumental scale, intricate ornamentation, and urban-planning principles characteristic of Timurid-era architecture.
-
D.
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.
-
E.
component of palace complex
A component of a palace complex is an individual architectural or functional unit—such as a hall, courtyard, gate, garden, or residential wing—that contributes to the overall structure, use, and symbolism of the palace ensemble.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:20 a.m.