Triple
T31448064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saalburg fort |
E802242
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reconstructed archaeological monument |
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 archaeological monument Context triple: [Saalburg fort, instanceOf, reconstructed archaeological monument]
-
A.
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.
-
B.
relocated monument
A relocated monument is a commemorative structure that has been physically moved from its original site to a new location while retaining its historical, cultural, or symbolic significance.
-
C.
reconstructed castle
A reconstructed castle is a historically inspired fortress or palace that has been rebuilt or extensively restored to approximate its original appearance and function, often using modern materials and techniques.
-
D.
ancient structure
An ancient structure is a man-made construction from antiquity, such as temples, fortifications, or monuments, that reflects the architectural techniques, cultural values, and historical context of its originating civilization.
-
E.
archaeological reserve
An archaeological reserve is a protected area designated to preserve, study, and manage archaeological sites and artifacts in situ for current and future research and education.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:11 p.m.