Triple
T25331985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singur |
E635173
|
entity |
| Predicate | courtCase |
P3996
|
FINISHED |
| Object | Singur land acquisition case |
—
|
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: Singur land acquisition case | Statement: [Singur, courtCase, Singur land acquisition case]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtCase Context triple: [Singur, courtCase, Singur land acquisition case]
-
A.
legalCase
chosen
Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
-
B.
courtIssue
Indicates that a court formally issues or hands down a legal document, order, ruling, or decision to the relevant parties.
-
C.
legalCasePresided
Indicates that a particular legal case was overseen and directed by a specific judge or judicial authority.
-
D.
courtCode
Indicates the specific court or judicial body associated with a legal case, proceeding, or record.
-
E.
legalCaseAlongside
Indicates that two or more legal cases are proceeding in parallel or in coordination, such that they are related or handled together in some aspect of the legal process.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497c72ffc81908aa380376bb068d3 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:30 p.m.