Triple
T29717806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kachwaha Rajputs |
E751962
|
entity |
| Predicate | presentDayDistribution |
P182406
|
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: [Kachwaha Rajputs, presentDayDistribution, Rajasthan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayDistribution Context triple: [Kachwaha Rajputs, presentDayDistribution, Rajasthan]
-
A.
presentDayRemains
Indicates that something from the past still exists or has surviving traces in the present day.
-
B.
presentDayDistrict
Indicates that one administrative district corresponds to or is located within the boundaries of a specified present-day district.
-
C.
presentDayIncludes
Indicates that the current day in a given calendar or time context encompasses or contains a specified time, date, or event.
-
D.
presentDayAccess
Indicates that an entity currently has the ability or permission to access another entity or resource in the present day.
-
E.
presentDayControl
Indicates that one entity currently holds authority, governance, or control over another entity in the present day.
- F. None of above. chosen
Provenance (4 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: April 28, 2026, 7:35 p.m.