Triple
T15242209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosehill Cemetery entrance gate |
E364285
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic cemetery gate |
C29722
|
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: historic cemetery gate Context triple: [Rosehill Cemetery entrance gate, instanceOf, historic cemetery gate]
-
A.
historic entrance
A historic entrance is a formally recognized point of access to a building or site that embodies significant architectural, cultural, or historical value from a particular period.
-
B.
cemetery architectural feature
chosen
A cemetery architectural feature is a designed structural or ornamental element within a burial ground—such as gates, mausoleums, monuments, pathways, or chapels—that shapes its spatial organization, symbolism, and visitor experience.
-
C.
cemetery
A cemetery is a designated outdoor area where the dead are buried or interred, often marked by gravestones, monuments, and pathways for visitors to mourn and remember.
-
D.
ancient city gate
An ancient city gate is a monumental architectural structure that controlled access to a fortified settlement, often serving defensive, ceremonial, and administrative functions.
-
E.
medieval city gate
A medieval city gate is a fortified architectural structure that controls access to a walled town or city, combining defensive features like towers and portcullises with symbolic and administrative functions.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:13 a.m.