Triple
T29566925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travancore-Cochin High Court |
E753186
|
entity |
| Predicate | apexJudicialBodyOf |
P153363
|
FINISHED |
| Object | Travancore-Cochin |
—
|
NE NERFINISHED |
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: Travancore-Cochin | Statement: [Travancore-Cochin High Court, apexJudicialBodyOf, Travancore-Cochin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apexJudicialBodyOf Context triple: [Travancore-Cochin High Court, apexJudicialBodyOf, Travancore-Cochin]
-
A.
judicialBody
Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
-
B.
judicialBodyName
Indicates the official name or title by which a judicial body (such as a court or tribunal) is designated.
-
C.
typeOfJurisdictionBody
Indicates that one entity functions as the jurisdictional authority or governing body for the other entity.
-
D.
tribunalConstitutedBy
Indicates that a tribunal is formed, established, or composed by a specified authority, body, or set of members.
-
E.
apexCourtOfState
chosen
Indicates that one entity serves as the highest judicial court (supreme court) within the jurisdiction of a particular state.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d4323708190a12d588bf6a512b3 |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:53 p.m.