Triple
T9972078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nehru Report |
E196230
|
entity |
| Predicate | proposedJudiciary |
P91378
|
FINISHED |
| Object | independent judiciary |
—
|
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: independent judiciary | Statement: [Nehru Report, proposedJudiciary, independent judiciary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedJudiciary Context triple: [Nehru Report, proposedJudiciary, independent judiciary]
-
A.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
-
B.
judiciaryAct
Indicates that an entity is involved in, established by, or otherwise directly related to a specific judiciary act or piece of judicial legislation.
-
C.
claimsJudiciaryHas
Indicates that a subject asserts or maintains that the judiciary possesses or holds a particular attribute, power, or characteristic.
-
D.
judicialBody
Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
-
E.
nominatedToDistrictCourtBy
Indicates that one entity formally selected or proposed another entity for a position on a district court.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7bb03688190a3f4fc1988b8fafa |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:48 p.m.