Triple
T26508984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatpurusha |
E669626
|
entity |
| Predicate | hasDevanagariName |
P36892
|
FINISHED |
| Object | तत्पुरुष |
—
|
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: तत्पुरुष | Statement: [Tatpurusha, hasDevanagariName, तत्पुरुष]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevanagariName Context triple: [Tatpurusha, hasDevanagariName, तत्पुरुष]
-
A.
nameInDevanagari
chosen
Indicates that an entity’s name is written or represented using the Devanagari script.
-
B.
hasNameInTeluguScript
Indicates that an entity is associated with a name written in the Telugu script.
-
C.
hasNameInIndia
Indicates that an entity is known or referred to by a particular name specifically within the context of India.
-
D.
hasNameInGujarati
Indicates that an entity is associated with a specific name expressed in the Gujarati language.
-
E.
hasNameInOdia
Indicates that an entity is associated with a specific name expressed in the Odia 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 27, 2026, 1:18 a.m.