Triple
T3197572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madras High Court |
E66969
|
entity |
| Predicate | oneOfCharteredHighCourts |
P46061
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Madras High Court, oneOfCharteredHighCourts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfCharteredHighCourts Context triple: [Madras High Court, oneOfCharteredHighCourts, true]
-
A.
originalJurisdictionOfHighCourt
Indicates that a particular matter or case falls within the High Court’s original jurisdiction to hear and decide it as a court of first instance.
-
B.
highestCourtOf
Indicates that one entity is the supreme judicial authority or top-level court within the jurisdiction or legal system of another entity.
-
C.
highCourtSeat
Indicates that a location serves as the official seat or headquarters of a high court.
-
D.
higherCourtOf
Indicates that one court has legal authority to review, overrule, or supervise the decisions and actions of another, lower court in the judicial hierarchy.
-
E.
highCourtBench
Indicates that a particular bench or panel of judges belongs to, or is constituted within, a high 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada7192994819084817307065a25e2 |
completed | March 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.