Triple
T8510354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taurica |
E201436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient geographical name |
C12509
|
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 name Context triple: [Taurica, instanceOf, ancient geographical 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.
historical geographic entity
chosen
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.
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.
-
D.
geographical names authority
A geographical names authority is an entity or system responsible for standardizing, maintaining, and providing authoritative information on the official names and spellings of geographic places.
-
E.
Vedic hydronym
A Vedic hydronym is a proper name of a river, stream, or other water body attested in the Vedic texts of ancient India, often carrying religious, mythological, or geographical significance.
- 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:15 p.m.