Triple
T33369983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madhubani |
E854460
|
entity |
| Predicate | regionLanguageGroup |
P10892
|
FINISHED |
| Object | Indo-Aryan languages |
—
|
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: Indo-Aryan languages | Statement: [Madhubani, regionLanguageGroup, Indo-Aryan languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionLanguageGroup Context triple: [Madhubani, regionLanguageGroup, Indo-Aryan languages]
-
A.
regionLanguageType
Indicates the type or category of language associated with a given region.
-
B.
regionLanguage
chosen
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
C.
languageGroupName
Indicates the name assigned to a particular language group or linguistic classification.
-
D.
languageGroupType
Indicates the classification relationship that specifies what type or category a particular language group belongs to.
-
E.
languageGroupAncestor
Indicates that one language group is an ancestor (historical or genealogical predecessor) of another language group in a language family.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:35 a.m.