Triple
T36887334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lacinion |
E911645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient geographical location |
C35265
|
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 geographical location Context triple: [Lacinion, instanceOf, ancient geographical location]
-
A.
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.
-
B.
ancient territory
An ancient territory is a historically defined geographic region that was controlled, inhabited, or claimed by past civilizations or cultures, often with distinct political, cultural, or religious significance.
-
C.
ancient place
chosen
An ancient place is a historically significant location from antiquity, often associated with early civilizations, archaeological remains, or long-standing cultural traditions.
-
D.
geographical region
A geographical region is a defined area of the Earth's surface characterized by shared physical, cultural, political, or environmental features that distinguish it from surrounding areas.
-
E.
ancient country
An ancient country is a historically significant territorial and political entity that existed in antiquity, characterized by its own culture, governance, and defined geographic boundaries.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.