Triple
T23489764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Short Service Commission |
E570636
|
entity |
| Predicate | rankOnCommission |
P124515
|
FINISHED |
| Object | Lieutenant (Indian Army) |
—
|
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: Lieutenant (Indian Army) | Statement: [Short Service Commission, rankOnCommission, Lieutenant (Indian Army)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankOnCommission Context triple: [Short Service Commission, rankOnCommission, Lieutenant (Indian Army)]
-
A.
typicalRankOnCommission
Indicates the usual or standard rank an individual holds while serving on a particular commission.
-
B.
commissionStatus
Indicates the current state or phase of a commission-related process, such as whether it is pending, active, completed, or cancelled.
-
C.
commissionType
Indicates the specific kind or category of commission arrangement that applies to a given transaction or relationship.
-
D.
unit2Commissioned
Indicates that a second unit has been formally placed into active service or operation.
-
E.
rankUponCommissioning
chosen
Indicates the military or official rank an individual holds at the moment they are formally commissioned into service or a specific role.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dba7388190a322ab059bb6522a |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:04 p.m.