Triple
T4147287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tophet of Carthage |
E89815
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Phoenician-Punic religious site |
C2557
|
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: Phoenician-Punic religious site Context triple: [Tophet of Carthage, instanceOf, Phoenician-Punic religious site]
-
A.
ancient Greek sanctuary
An ancient Greek sanctuary is a sacred precinct dedicated to one or more deities, typically containing temples, altars, votive offerings, and ritual spaces where religious ceremonies, festivals, and oracles took place.
-
B.
ancient sanctuary
chosen
An ancient sanctuary is a sacred, often secluded place dedicated to worship, ritual, or protection, typically imbued with religious or spiritual significance by past civilizations.
-
C.
ancient Roman monument
An ancient Roman monument is a large, enduring structure or commemorative work built by the Romans to honor deities, leaders, victories, or civic achievements, often showcasing advanced engineering and classical architectural styles.
-
D.
ancient Roman temple
An ancient Roman temple is a monumental religious structure, typically rectangular with a columned portico and elevated podium, dedicated to one or more deities and serving as a focal point for public worship and civic identity in Roman society.
-
E.
Jewish pilgrimage site
A Jewish pilgrimage site is a location of religious and historical significance in Judaism to which individuals or communities travel, traditionally or in contemporary practice, for prayer, commemoration, and spiritual connection.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:43 p.m.