Triple
T21097308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onogurs |
E519799
|
entity |
| Predicate | territorialRange |
P2178
|
FINISHED |
| Object | north of the Black Sea |
—
|
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 Black Sea | Statement: [Onogurs, territorialRange, north of the Black Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territorialRange Context triple: [Onogurs, territorialRange, north of the Black Sea]
-
A.
geographicRangeType
Indicates the kind of geographic range or distribution pattern that characterizes where an entity occurs or is found.
-
B.
territorialExtent
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
-
C.
geographicRangeTrend
Indicates how the spatial extent or distribution area of something is changing over time (e.g., expanding, contracting, or remaining stable).
-
D.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
E.
geographicDistribution
chosen
Indicates the spatial range or area over which something occurs, exists, or is found.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b5a3a9481908e30fba9717dc461 |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:52 p.m.