Triple
T1089709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court of India |
E24132
|
entity |
| Predicate | hearsPublicInterestLitigation |
P16126
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Supreme Court of India, hearsPublicInterestLitigation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearsPublicInterestLitigation Context triple: [Supreme Court of India, hearsPublicInterestLitigation, yes]
-
A.
hearsCasesAgainst
Indicates that one party (typically a judicial body or official) formally listens to and considers legal cases brought against another party.
-
B.
hearsAppealsBy
Indicates that one party has the authority or role to review and decide on appeals submitted by another party.
-
C.
heldPublicHearings
Indicates that formal meetings open to the public were conducted to gather input, discuss issues, or present information.
-
D.
hears
Indicates that one entity perceives or detects sounds produced by another entity or source.
-
E.
hearsCasesUnder
chosen
Indicates that a judicial body or authority has the responsibility and power to adjudicate legal cases falling within a specified jurisdiction, category, or scope.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b97f216881909e9b8943ce2078e4 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b741b0cc8190be001a16a81f6d9e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.