Triple
T25115548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panchayati Raj |
E629116
|
entity |
| Predicate | languageOriginOfTerm |
P121450
|
FINISHED |
| Object | Sanskrit |
—
|
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: Sanskrit | Statement: [Panchayati Raj, languageOriginOfTerm, Sanskrit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOriginOfTerm Context triple: [Panchayati Raj, languageOriginOfTerm, Sanskrit]
-
A.
languageOfCoinedTerm
chosen
Indicates the language in which a particular term was originally coined or first formulated.
-
B.
etymologicalSource
Indicates that one term or name originates from, is derived from, or has its roots in another term or name.
-
C.
etymologyContext
Indicates the contextual or situational background (such as time, place, culture, or domain) relevant to the origin and historical development of a word or term.
-
D.
etymologicalRootMeaning
Indicates that one term’s meaning originates from or is derived from the historical or original meaning of another term.
-
E.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 18, 2026, 6:27 a.m.