Triple
T19737178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L’Arc |
E474016
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | structure in an architectural complex |
C34066
|
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: structure in an architectural complex Context triple: [L’Arc, instanceOf, structure in an architectural complex]
-
A.
ancient building complex
An ancient building complex is a historically significant group of interconnected or closely situated structures, often serving religious, political, residential, or commercial functions within a past civilization.
-
B.
institutional building complex
An institutional building complex is a coordinated group of structures and shared spaces designed to support the functions, services, and administration of an organization such as a university, hospital, or government entity.
-
C.
component of palace complex
chosen
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.
-
D.
architectural ensemble
An architectural ensemble is a coherent group of buildings and spaces designed or evolved together to form a unified, contextually integrated spatial and aesthetic whole.
-
E.
masonry structure complex
A masonry structure complex is a group of interconnected or related buildings, walls, and other constructed elements primarily made of stone, brick, or concrete masonry units that function together as a unified built environment.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:47 p.m.