Triple
T17709547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyadski Vorota monument |
E441526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reconstructed historical gateway |
C8110
|
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: reconstructed historical gateway Context triple: [Lyadski Vorota monument, instanceOf, reconstructed historical gateway]
-
A.
historic gateway and bridge
A historic gateway and bridge is an architectural structure that combines a monumental entrance passage with a spanning construction over a physical obstacle, often serving both defensive and ceremonial functions while facilitating transit.
-
B.
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.
-
C.
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.
-
D.
reconstructed historic site
chosen
A reconstructed historic site is a place where buildings, structures, or environments from the past have been rebuilt or significantly restored to approximate their original appearance and context for educational, commemorative, or touristic purposes.
-
E.
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.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:05 a.m.