Triple
T34219963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moksha |
E877895
|
entity |
| Predicate | folkloreLanguage |
P22041
|
FINISHED |
| Object | Moksha language |
—
|
NE NERFINISHED |
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: Moksha language | Statement: [Moksha, folkloreLanguage, Moksha language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: folkloreLanguage Context triple: [Moksha, folkloreLanguage, Moksha language]
-
A.
folkloreFunction
Indicates that something serves a role, purpose, or function within a body of folklore, such as myths, legends, or traditional narratives.
-
B.
languageOfMyths
chosen
Indicates that the subject is the language in which the myths associated with the object are told or recorded.
-
C.
includesFolklore
Indicates that one entity contains, incorporates, or features folklore as part of its content or composition.
-
D.
countryOfFolklore
Indicates the country with which a particular piece or tradition of folklore is associated or from which it originates.
-
E.
languageTraditions
Indicates that there is a relationship between entities involving the customs, practices, and conventions associated with the use, preservation, or transmission of a particular language.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71081727c819096d2462bf0fd4b26 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.