Triple
T18658194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acesines |
E456121
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient place name |
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 place name Context triple: [Acesines, instanceOf, ancient place name]
-
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.
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.
-
C.
Aboriginal place name
An Aboriginal place name is a geographic name derived from the languages and cultural traditions of Indigenous Australian peoples, often reflecting features of the land, water, flora, fauna, or ancestral stories associated with that location.
-
D.
Old Persian toponym
An Old Persian toponym is a place name recorded in the Old Persian language, typically found in Achaemenid royal inscriptions and related texts, designating geographic locations within or beyond the Persian Empire.
-
E.
ancient Greek name
An ancient Greek name is a personal identifier originating from the language, mythology, history, and cultural practices of ancient Greece, often reflecting virtues, gods, heroes, or familial lineage.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.