Triple
T14491210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhima I |
E359365
|
entity |
| Predicate | motherTongueLikely |
P151
|
FINISHED |
| Object | Old Gujarati |
—
|
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: Old Gujarati | Statement: [Bhima I, motherTongueLikely, Old Gujarati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motherTongueLikely Context triple: [Bhima I, motherTongueLikely, Old Gujarati]
-
A.
motherTongueRegion
Indicates the geographic region where an entity’s native or primary language is predominantly spoken or originates.
-
B.
parentLanguage
Indicates that one language is the ancestral or source language from which another language is derived or historically developed.
-
C.
nativeLanguage
chosen
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
D.
primaryLanguageHeritage
Indicates that one language is the main ancestral or culturally inherited language associated with an entity.
-
E.
laterLanguageDominant
Indicates that one language becomes the dominant or primary language for an entity at a later point in time, after another language previously held that role.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930d820481908b9813014dd02540 |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:20 a.m.