Triple
T15655332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mordvinic languages |
E376423
|
entity |
| Predicate | standardVarieties |
P59038
|
FINISHED |
| Object | standard Erzya |
—
|
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: standard Erzya | Statement: [Mordvinic languages, standardVarieties, standard Erzya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardVarieties Context triple: [Mordvinic languages, standardVarieties, standard Erzya]
-
A.
standardVarietyBasedIn
Indicates that a standard or reference variety (such as a language or dialect) is primarily established, recognized, or centered in a particular location or region.
-
B.
typicalVariety
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
-
C.
notableVarieties
chosen
Indicates that there are specific, distinguished types or versions associated with an entity that are recognized as notable.
-
D.
numberOfPrimaryVarieties
Indicates the count of distinct primary varieties associated with a given entity.
-
E.
hasVarietyOf
Indicates that an entity possesses or offers multiple different types, forms, or versions of something.
- 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.