Triple
T3974122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Medical Service |
E85598
|
entity |
| Predicate | allowedRank |
P34581
|
FINISHED |
| Object | commissioned officer |
—
|
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: commissioned officer | Statement: [Indian Medical Service, allowedRank, commissioned officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedRank Context triple: [Indian Medical Service, allowedRank, commissioned officer]
-
A.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
B.
rankRestriction
Indicates a constraint or limit placed on the rank or hierarchical level that an entity may hold within a given system or structure.
-
C.
hasRankLevels
chosen
Indicates that an entity is associated with one or more hierarchical rank levels within a ranking or grading system.
-
D.
isRank
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
-
E.
usesRank
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
- 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:32 p.m.