Triple
T38030272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dausa Lok Sabha constituency |
E948887
|
entity |
| Predicate | majorDistrictCovered |
P22582
|
FINISHED |
| Object | Dausa district |
—
|
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: Dausa district | Statement: [Dausa Lok Sabha constituency, majorDistrictCovered, Dausa district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorDistrictCovered Context triple: [Dausa Lok Sabha constituency, majorDistrictCovered, Dausa district]
-
A.
majorDistrict
Indicates that one administrative district is the primary or most significant district associated with another entity or area.
-
B.
notableDistrictCovered
Indicates that a place or entity includes within its area a district that is considered notable or significant.
-
C.
includesDistrict
chosen
Indicates that one administrative or geographic entity contains or encompasses a specific district within its boundaries.
-
D.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
E.
isMainDistrictOf
Indicates that a district serves as the primary or central administrative district of a specified larger area or jurisdiction.
- 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a003ffb548081908ba64fd2b570f42f |
completed | May 10, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_6a003fcecf788190a13dff38b9de3414 |
completed | May 10, 2026, 8:20 a.m. |
Created at: May 3, 2026, 4:20 p.m.