Triple
T4985076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jammu & Kashmir National Conference |
E111979
|
entity |
| Predicate | positionOnArticle370 |
P20467
|
FINISHED |
| Object | opposed abrogation of Article 370 |
—
|
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 370 | Statement: [Jammu & Kashmir National Conference, positionOnArticle370, opposed abrogation of Article 370]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnArticle370 Context triple: [Jammu & Kashmir National Conference, positionOnArticle370, opposed abrogation of Article 370]
-
A.
positionOnIssue
chosen
Indicates the stance or viewpoint an entity holds regarding a specific issue or topic.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionOnReason
Indicates that one entity holds a particular stance, justification, or rationale concerning another entity or issue.
-
E.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
- 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.