Triple
T6127053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Police Service |
E136619
|
entity |
| Predicate | allocationLevel |
P7279
|
FINISHED |
| Object | state cadre |
—
|
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: state cadre | Statement: [Indian Police Service, allocationLevel, state cadre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allocationLevel Context triple: [Indian Police Service, allocationLevel, state cadre]
-
A.
designationLevel
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
B.
classificationLevel
chosen
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
C.
configurationLevel
Indicates the degree or tier of settings or parameters applied to configure something within a system or context.
-
D.
assessmentLevel
Indicates the degree, rating, or intensity assigned to an evaluation or judgment of something.
-
E.
representedLevel
Indicates that one entity denotes or encodes the degree, intensity, or value (i.e., the level) of another entity or property.
- 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c2a13a48190b80e11d58fc87c8a |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:15 p.m.