Triple
T19748391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praetorium of Pontius Pilate |
E474312
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman administrative headquarters |
C42564
|
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: Roman administrative headquarters Context triple: [Praetorium of Pontius Pilate, instanceOf, Roman administrative headquarters]
-
A.
Roman imperial residence
A Roman imperial residence is a grand, often fortified palace complex that served as the official home, administrative center, and ceremonial stage for the Roman emperor and his court.
-
B.
Roman town
A Roman town is an urban settlement in the Roman Empire characterized by planned streets, public buildings such as forums, baths, and temples, and a structured social and administrative organization under Roman law and culture.
-
C.
Roman military camp
A Roman military camp is a temporary or permanent fortified encampment laid out in a standardized, highly organized grid pattern to house, protect, and support Roman troops during campaigns.
-
D.
Byzantine imperial palace
A Byzantine imperial palace is a grand, fortified residential and ceremonial complex that housed the emperor and court, combining administrative, religious, and domestic functions in richly decorated architectural spaces.
-
E.
Byzantine city
A Byzantine city is an urban center of the Eastern Roman (Byzantine) Empire characterized by fortified walls, Christian religious institutions, administrative and commercial hubs, and a blend of Greco-Roman and Eastern cultural influences.
- F. None of above. chosen
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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:47 p.m.