Triple
T37315014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neelkanth |
E926309
|
entity |
| Predicate | DevanagariForm |
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: [Neelkanth, DevanagariForm, नीलकण्ठ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DevanagariForm Context triple: [Neelkanth, DevanagariForm, नीलकण्ठ]
-
A.
nameInDevanagari
chosen
Indicates that an entity’s name is written or represented using the Devanagari script.
-
B.
characterFormationMethod
Indicates the process or technique by which a character is created, developed, or brought into existence.
-
C.
hasDrutamAksharas
Indicates that something possesses or is associated with a specific number of drutam rhythmic units (aksharas) in a metrical or musical context.
-
D.
positionOnIndusScript
Indicates that one entity occupies a specific positional location relative to another entity within the context of Indus script inscriptions or signs.
-
E.
hasGranthaConsonants
Indicates that an entity includes or makes use of consonant characters from the Grantha script.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.