Triple
T33000236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beit She'arim National Park |
E844345
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Jewish necropolis |
C51282
|
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: ancient Jewish necropolis Context triple: [Beit She'arim National Park, instanceOf, ancient Jewish necropolis]
-
A.
Phoenician necropolis
A Phoenician necropolis is a burial complex or cemetery used by the ancient Phoenician civilization, typically featuring rock-cut tombs, sarcophagi, and grave goods that reflect their funerary practices and beliefs about the afterlife.
-
B.
Sephardic burial ground
A Sephardic burial ground is a cemetery designated for the interment of Jews of Sephardic heritage, reflecting their distinct religious customs, cultural traditions, and historical communities.
-
C.
ancient Egyptian burial ground
An ancient Egyptian burial ground is a designated sacred area where Egyptians of antiquity interred the dead, often featuring tombs, grave goods, and ritual structures reflecting their beliefs about the afterlife.
-
D.
funerary site
chosen
A funerary site is a designated place where human or animal remains are buried, entombed, or otherwise ritually deposited, often accompanied by structures, markers, or artifacts related to death and commemoration.
-
E.
Nabataean tomb
A Nabataean tomb is a rock-cut or freestanding funerary monument, typically carved into sandstone cliffs and characterized by a blend of local, Hellenistic, and Near Eastern architectural elements, used by the Nabataean civilization to bury and honor their dead.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.