Triple
T23776703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babylon (as prisoner, according to 2 Chronicles) |
E587695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical location role |
C7977
|
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: historical location role Context triple: [Babylon (as prisoner, according to 2 Chronicles), instanceOf, historical location role]
-
A.
historical place name
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.
-
B.
historical geographic entity
A historical geographic entity is a spatially bounded area whose location, extent, or political status has changed or ceased to exist over time, but which is recognized for its past geographic or administrative significance.
-
C.
historic locality
A historic locality is a geographically defined place recognized for its significant past events, cultural heritage, or historical importance.
-
D.
historical position
chosen
A historical position is a specific role, office, or status held by an individual within a past social, political, or cultural context, defined by its responsibilities, authority, and time period.
-
E.
معلم تاريخي
المعلم التاريخي هو موقع أو مبنى أو عنصر مادي يرتبط بأحداث أو شخصيات أو حقب تاريخية مهمة ويُحافظ عليه بوصفه شاهدًا على الماضي وذاكرةً ثقافية للمجتمع.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:16 p.m.