Triple
T1197865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Police Service |
E25708
|
entity |
| Predicate | hasCadreSystem |
P16512
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Indian Police Service, hasCadreSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCadreSystem Context triple: [Indian Police Service, hasCadreSystem, true]
-
A.
cadreSystem
chosen
Indicates a structured system for managing, organizing, and overseeing personnel or leadership positions within an institution or organization.
-
B.
hasCadetBranch
Indicates that one lineage, family, or house is a junior or offshoot branch derived from another main or senior line.
-
C.
hasCadetRank
Indicates that an entity holds or is assigned a cadet-level rank within a hierarchical or military-style ranking system.
-
D.
hasCorpsOfCadets
Indicates that an institution maintains an organized corps of cadets as part of its structure or programs.
-
E.
hasOrganizationalStructure
Indicates that an entity possesses a defined internal arrangement of roles, responsibilities, and relationships that determine how it is organized and operates.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9c013c8190822d44d465d60fdb |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.