Triple
T37087816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Court |
E918336
|
entity |
| Predicate | appointmentConsultedWith |
P9345
|
FINISHED |
| Object | Chief Justice of India |
—
|
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: Chief Justice of India | Statement: [High Court, appointmentConsultedWith, Chief Justice of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointmentConsultedWith Context triple: [High Court, appointmentConsultedWith, Chief Justice of India]
-
A.
publicConsultationHeld
Indicates that a formal public consultation process has been conducted regarding a particular decision, policy, or project.
-
B.
appointmentOnAdviceOf
chosen
Indicates that an appointment or selection of someone to a position is made based on the recommendation, counsel, or formal advice of another person or authority.
-
C.
appointmentScheduledVia
Indicates that an appointment was scheduled using a particular method, channel, or system.
-
D.
consultationDate
Indicates the date on which a consultation between the relevant entities took place.
-
E.
mayConsultWith
Indicates that one entity is permitted or allowed to seek advice, guidance, or professional input from another entity.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:14 p.m.