Triple
T20229881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janata Parivar (historical association) |
E495485
|
entity |
| Predicate | coreIssues |
P57423
|
FINISHED |
| Object | social justice |
—
|
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: social justice | Statement: [Janata Parivar (historical association), coreIssues, social justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreIssues Context triple: [Janata Parivar (historical association), coreIssues, social justice]
-
A.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
B.
knownIssue
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
-
C.
structuralIssues
Indicates that there are problems or deficiencies in the design, construction, or integrity of a structure or system.
-
D.
underlyingIssue
Indicates that one situation, problem, or condition is the fundamental cause or root problem behind another.
-
E.
primaryIssue
chosen
Indicates that the related item is the main or most important issue among a set of issues.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fdc2590819089a946d16c6c0e59 |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.