Triple
T25115545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panchayati Raj |
E629116
|
entity |
| Predicate | firstIntroducedInState |
P24938
|
FINISHED |
| Object | Rajasthan |
—
|
NE NERFINISHED |
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: Rajasthan | Statement: [Panchayati Raj, firstIntroducedInState, Rajasthan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIntroducedInState Context triple: [Panchayati Raj, firstIntroducedInState, Rajasthan]
-
A.
introducedByState
chosen
Indicates that something (such as a law, policy, measure, or proposal) has been formally initiated or brought forward by a state or state-level authority.
-
B.
foundingState
Indicates that a state or entity played a primary role in establishing or creating another organization, institution, or political entity.
-
C.
foundingMemberState
Indicates that a state is one of the original founding members of an organization, union, or similar entity.
-
D.
stateFounded
Indicates that a particular state was established or created at a specific time or by a specific founding event or agent.
-
E.
stateFoundedIn
Indicates that a particular state was established or came into existence in a specified year or time period.
- 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_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 18, 2026, 6:27 a.m.