Triple
T23489288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Director General, Central Industrial Security Force |
E570625
|
entity |
| Predicate | rankIn |
P152574
|
FINISHED |
| Object | Indian Police Service |
—
|
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: Indian Police Service | Statement: [Director General, Central Industrial Security Force, rankIn, Indian Police Service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankIn Context triple: [Director General, Central Industrial Security Force, rankIn, Indian Police Service]
-
A.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
B.
rankIndicated
Indicates that one entity specifies, denotes, or reveals the hierarchical rank or level of another entity.
-
C.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
D.
rankingBehind
Indicates that one entity holds a lower or later position than another in an ordered ranking or hierarchy.
-
E.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dae8cc8190bf74d1bdb0fc6c60 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:04 p.m.