Triple
T29485667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Court of Manipur |
E747911
|
entity |
| Predicate | judicialAuthorityLevel |
P132640
|
FINISHED |
| Object | highest judicial authority in Manipur |
—
|
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: highest judicial authority in Manipur | Statement: [High Court of Manipur, judicialAuthorityLevel, highest judicial authority in Manipur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judicialAuthorityLevel Context triple: [High Court of Manipur, judicialAuthorityLevel, highest judicial authority in Manipur]
-
A.
judicialBranchLevel
Indicates the hierarchical level or tier within the judicial branch at which a given judicial body, office, or action operates.
-
B.
jurisdictionLevel
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
-
C.
hadCourtLevel
Indicates the specific hierarchical level of the court at which a legal case or judicial action took place.
-
D.
hasJudicialPowerLevel
chosen
Indicates that an entity possesses a specified degree or extent of judicial authority or decision-making power.
-
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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c05947c8190b34739a0a7c0201f |
completed | May 2, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:08 p.m.