Triple
T22297459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L. Chandra Kumar v. Union of India |
E551156
|
entity |
| Predicate | basicStructureDoctrine |
P4473
|
FINISHED |
| Object | reaffirmed |
—
|
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: reaffirmed | Statement: [L. Chandra Kumar v. Union of India, basicStructureDoctrine, reaffirmed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basicStructureDoctrine Context triple: [L. Chandra Kumar v. Union of India, basicStructureDoctrine, reaffirmed]
-
A.
createdDoctrine
Indicates that an entity originated, formulated, or established a particular doctrine, theory, or set of principles.
-
B.
definedDoctrineAt
Indicates that a particular doctrine was formally established, articulated, or codified at a specific place or time.
-
C.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
D.
usesDoctrine
chosen
Indicates that one entity applies, follows, or relies on a particular doctrine in its actions or reasoning.
-
E.
extendsDoctrineTo
Indicates that a doctrine, principle, or rule is applied or carried over from one context, entity, or domain to another, broadening its scope or coverage.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1572200c88190b9413286136fef15 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.