Triple
T5739183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Governments of India |
E126571
|
entity |
| Predicate | haveJudiciaryBranch |
P10526
|
FINISHED |
| Object | State 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: State Judiciary | Statement: [State Governments of India, haveJudiciaryBranch, State Judiciary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveJudiciaryBranch Context triple: [State Governments of India, haveJudiciaryBranch, State Judiciary]
-
A.
hasJudiciary
chosen
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
-
B.
hasBranchCourts
Indicates that an institution or main court maintains one or more subordinate or satellite courts under its jurisdiction.
-
C.
hasJudicialSeat
Indicates that an entity holds an official position or seat within a judicial body or court.
-
D.
hasJudicialOfficer
Indicates that an entity is associated with or served by a specific judicial officer (such as a judge or magistrate) responsible for legal or court-related functions.
-
E.
judicialBody
Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255dc35c8190ab9ee5d269ce553a |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.