Triple
T4985077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jammu & Kashmir National Conference |
E111979
|
entity |
| Predicate | positionOnArticle35A |
P9295
|
FINISHED |
| Object | opposed abrogation of Article 35A |
—
|
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: opposed abrogation of Article 35A | Statement: [Jammu & Kashmir National Conference, positionOnArticle35A, opposed abrogation of Article 35A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnArticle35A Context triple: [Jammu & Kashmir National Conference, positionOnArticle35A, opposed abrogation of Article 35A]
-
A.
positionOnIssue
Indicates the stance or viewpoint an entity holds regarding a specific issue or topic.
-
B.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
C.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
D.
positionOnLaw
chosen
Indicates a stance, opinion, or interpretation that an entity holds regarding a specific law or legal provision.
-
E.
positionOnRights
Indicates a stance, opinion, or policy an entity holds regarding rights (such as legal, human, or civil rights).
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.