Triple
T20320495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arimathea (traditional identification) |
E492194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional identification of a place |
C4613
|
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: traditional identification of a place Context triple: [Arimathea (traditional identification), instanceOf, traditional identification of a place]
-
A.
ancient place
An ancient place is a historically significant location from antiquity, often associated with early civilizations, archaeological remains, or long-standing cultural traditions.
-
B.
historical place name
chosen
A historical place name is a designation for a geographic location that reflects its identity, usage, or significance during a specific past period, which may differ from its modern name or boundaries.
-
C.
territorial designation
A territorial designation is a formal label or title that identifies and defines a specific geographic area or jurisdiction for political, administrative, or legal purposes.
-
D.
location
A location is a specific place or position in physical or virtual space that can be identified, referenced, and used to describe where entities or events exist or occur.
-
E.
traditional area
A traditional area is a geographically defined region recognized for its longstanding cultural, historical, or customary significance, often governed by inherited practices and community norms.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:20 a.m.