Triple
T4076773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulu |
E86782
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Jain Tulu |
E86782
|
NE 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: Jain Tulu | Statement: [Tulu, hasDialect, Jain Tulu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jain Tulu Context triple: [Tulu, hasDialect, Jain Tulu]
-
A.
Tulu
chosen
Tulu is a Dravidian language spoken primarily in the coastal regions of Karnataka and northern Kerala in southwestern India, known for its rich oral traditions and distinct cultural identity.
-
B.
Nagpuri
Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
-
C.
Kurukh
Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
-
D.
Mirpuri
Mirpuri is a major dialect of the Lahnda (Western Punjabi) language, primarily spoken in the Mirpur region of Azad Kashmir and among its diaspora communities.
-
E.
Sant Bhasha
Sant Bhasha is a historical North Indian devotional literary language used in Sikh and related spiritual poetry, written in the Gurmukhi script.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4ba3f08190a6c6aaf6e9c99bd5 |
completed | March 9, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5769bafbc8190b14fb80b663b3747 |
completed | March 14, 2026, 2:54 p.m. |
Created at: March 9, 2026, 3:39 p.m.