Triple
T15655312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mordvinic languages |
E376423
|
entity |
| Predicate | areal |
P106583
|
FINISHED |
| Object | Volga region |
—
|
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: Volga region | Statement: [Mordvinic languages, areal, Volga region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areal Context triple: [Mordvinic languages, areal, Volga region]
-
A.
arealFeature
Indicates a relationship where something is characterized as a spatial or geographic feature occupying an area on a surface or map.
-
B.
area
Indicates that one entity has a measured two-dimensional extent or surface size quantified by another entity.
-
C.
arealTypology
chosen
Indicates a typological relationship based on geographic or areal distribution, showing how linguistic features are shared or patterned across regions.
-
D.
arealRegion
Indicates that something occupies or pertains to a specific two-dimensional geographic or spatial area.
-
E.
arealCluster
Indicates that entities belong to the same spatially contiguous or closely grouped geographic area.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef1f83c8190bbf65eed162cbd55 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.