Triple
T12376150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patna High Court |
E295127
|
entity |
| Predicate | hasPowerOfJudicialReview |
P53035
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Patna High Court, hasPowerOfJudicialReview, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerOfJudicialReview Context triple: [Patna High Court, hasPowerOfJudicialReview, Yes]
-
A.
hasConstitutionalReview
chosen
Indicates that an authority or body has the power to examine and judge the conformity of laws or actions with a constitution.
-
B.
hasJudicialPowerSource
Indicates the source or origin from which an entity derives its judicial authority or power.
-
C.
judicialReviewBy
Indicates that a judicial body examines and evaluates the legality or constitutionality of an action, decision, or rule made by another authority.
-
D.
isConstitutionalAuthority
Indicates that an entity holds recognized legal or institutional power derived from or defined by a constitution.
-
E.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93fb8d6c081909e8bbbd52c73f29c |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.