Triple
T35177380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimmerioi |
E1015745
|
entity |
| Predicate | possibleOriginRegion |
P410
|
FINISHED |
| Object | north of the Caucasus |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: north of the Caucasus | Statement: [Kimmerioi, possibleOriginRegion, north of the Caucasus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleOriginRegion Context triple: [Kimmerioi, possibleOriginRegion, north of the Caucasus]
-
A.
sourceRegion
chosen
Indicates the geographic or spatial region from which something originates or is derived.
-
B.
recipientRegion
Indicates the geographic region that receives or is the destination of a transfer, delivery, or directed action.
-
C.
isFromRegion
Indicates that one entity originates from, is associated with, or belongs to a specified geographic region.
-
D.
hasTypicalGeographicOrigin
Indicates that an entity is commonly or characteristically associated with originating from a particular geographic location.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- F. None of above.
Provenance (3 batches)
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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:02 p.m.