Triple
T14052355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All India Judicial Service |
E338121
|
entity |
| Predicate | benefitClaimed |
P2188
|
FINISHED |
| Object | greater objectivity in judicial appointments |
—
|
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: greater objectivity in judicial appointments | Statement: [All India Judicial Service, benefitClaimed, greater objectivity in judicial appointments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitClaimed Context triple: [All India Judicial Service, benefitClaimed, greater objectivity in judicial appointments]
-
A.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
B.
resultOfClaim
Indicates that something occurs as a consequence or outcome of a specific claim or assertion.
-
C.
claimProcess
Indicates the process by which a claim (such as an insurance or service claim) is received, evaluated, and resolved between involved parties.
-
D.
capitalClaimed
Indicates that an entity asserts or designates another entity as its capital.
-
E.
hasBenefit
chosen
Indicates that one entity provides an advantage, improvement, or positive outcome to 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8bc54c8190a12f0fc056568538 |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.