Triple
T26995175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajasthan Police |
E679962
|
entity |
| Predicate | policeStationsIn |
P21775
|
FINISHED |
| Object | all districts of Rajasthan |
—
|
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: all districts of Rajasthan | Statement: [Rajasthan Police, policeStationsIn, all districts of Rajasthan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeStationsIn Context triple: [Rajasthan Police, policeStationsIn, all districts of Rajasthan]
-
A.
hasPoliceStationsIn
chosen
Indicates that one entity possesses, manages, or contains one or more police stations located within the area or jurisdiction of another entity.
-
B.
policePrecinct
Indicates that a specified location, building, or area functions as or is designated as a police precinct.
-
C.
hasPoliceInstitution
Indicates that an entity is associated with, governed by, or served by a particular police institution or law enforcement body.
-
D.
railwayStationInDistrict
Indicates that a railway station is located within and administratively belongs to a specific district.
-
E.
hasFireStation
Indicates that a location or area contains or is served by a fire station.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 6:54 a.m.