Triple
T11739583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janata Party |
E279116
|
entity |
| Predicate | internalConflictOver |
P1406
|
FINISHED |
| Object | dual membership of RSS |
—
|
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: dual membership of RSS | Statement: [Janata Party, internalConflictOver, dual membership of RSS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalConflictOver Context triple: [Janata Party, internalConflictOver, dual membership of RSS]
-
A.
internalConflict
Indicates a relationship where an entity experiences opposing desires, beliefs, or motives within itself, leading to psychological or emotional tension.
-
B.
conflictIn
chosen
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
D.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
E.
facesConflictWith
Indicates that one entity is in opposition, dispute, or contention with another, involving incompatible goals, interests, or actions.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f025f88190a39280806c9d7c33 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.