Triple
T6127090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All India Services |
E136620
|
entity |
| Predicate | officersServeAs |
P68298
|
FINISHED |
| Object | district magistrates |
—
|
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: district magistrates | Statement: [All India Services, officersServeAs, district magistrates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officersServeAs Context triple: [All India Services, officersServeAs, district magistrates]
-
A.
officersAre
Indicates that certain individuals hold the role or position of officers within a specified group, organization, or context.
-
B.
commissionsOfficersFor
Indicates that an authority or organization formally appoints or authorizes individuals to serve as officers.
-
C.
isOfficerOf
Indicates that one entity holds an official position, role, or office within another entity (such as an organization, group, or institution).
-
D.
servesAsOfficeOf
Indicates that one entity functions as the official office, headquarters, or administrative base for another entity.
-
E.
officerCorps
Indicates that an entity belongs to, is part of, or is associated with a group or body of officers within an organization or institution.
- 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_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. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:15 p.m.