Triple

T34933445
Position Surface form Disambiguated ID Type / Status
Subject Tarn Taran District Court E1007503 entity
Predicate partOf P40 FINISHED
Object Punjab judiciary
The Punjab judiciary is the system of courts and judicial institutions responsible for administering justice and interpreting laws within the Indian state of Punjab.
E10207 NE 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: Punjab judiciary | Statement: [Tarn Taran District Court, partOf, Punjab judiciary]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Punjab judiciary
Triple: [Tarn Taran District Court, partOf, Punjab judiciary]
Generated description
The Punjab judiciary is the system of courts and judicial institutions responsible for administering justice and interpreting laws within the Indian state of Punjab.

Provenance (5 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_69f76dc513fc819084a1ff52abbfa5bc completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78256da08819096744eed341fcf0a completed May 3, 2026, 5:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37a8bb294c8190aca59e7ab62be67c completed June 21, 2026, 9:02 a.m.
NEDg Description generation batch_6a37a9cd9850819094e07e59e8dedc96 completed June 21, 2026, 9:07 a.m.
NED2 Entity disambiguation (via description) batch_6a37abd05f4c819089833309fc436419 completed June 21, 2026, 9:16 a.m.
Created at: May 3, 2026, 4 p.m.